Skip to content

Commit 5b5a2ce

Browse files
chrisdachrisda
authored
Merge pull request MicrosoftDocs#3573 from denisebmsft/EDM-deniseb
EDM deniseb
2 parents 140d9cc + 5e008f1 commit 5b5a2ce

File tree

5 files changed

+424
-1
lines changed

5 files changed

+424
-1
lines changed

‎exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
applicable: Office 365 Security & Compliance Center
4+
title: Get-DlpEdmSchema
5+
schema: 2.0.0
6+
author: chrisda
7+
ms.author: chrisda
8+
ms.reviewer:
9+
monikerRange: "o365scc-ps"
10+
---
11+
12+
# Get-DlpEdmSchema
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the Office 365 Security & Compliance Center. For more information, see Office 365 Security & Compliance Center PowerShell (https://technet.microsoft.com/library/mt587091.aspx).
16+
17+
Use the Get-DlpEdmSchema cmdlet to view exact data match (EDM) data loss prevention (DLP) schemas in the Security & Compliance Center.
18+
19+
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
20+
21+
## SYNTAX
22+
23+
```
24+
Get-DlpEdmSchema [[-Identity] <EdmStorageIdParameter>] [<CommonParameters>]
25+
```
26+
27+
## DESCRIPTION
28+
You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in Office 365 Security & Compliance Center (https://go.microsoft.com/fwlink/p/?LinkId=511920).
29+
30+
## EXAMPLES
31+
32+
### -------------------------- Example 1 --------------------------
33+
```
34+
Get-DlpEdmSchema
35+
```
36+
37+
This example returns a summary list of all DLP EDM schemas in the organization.
38+
39+
### -------------------------- Example 2 --------------------------
40+
```
41+
Get-DlpEdmSchema -Identity "Schema for Patient Records"
42+
```
43+
44+
This example returns detailed information for the DLP EDM schema named Schema for patient Records.
45+
46+
## PARAMETERS
47+
48+
### -Identity
49+
The Identity parameter specifies the DLP EDM schema that you want to view. You can use any value that uniquely identifies the schema. For example:
50+
51+
- Name
52+
53+
- Distinguished name (DN)
54+
55+
```yaml
56+
Type: EdmStorageIdParameter
57+
Parameter Sets: (All)
58+
Aliases:
59+
Applicable: Office 365 Security & Compliance Center
60+
Required: False
61+
Position: 0
62+
Default value: None
63+
Accept pipeline input: True (ByPropertyName, ByValue)
64+
Accept wildcard characters: False
65+
```
66+
67+
### CommonParameters
68+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
69+
70+
## INPUTS
71+
72+
###
73+
74+
## OUTPUTS
75+
76+
###
77+
78+
## NOTES
79+
80+
## RELATED LINKS
81+
82+
[Online Version](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema)
83+
84+
[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/office365/securitycompliance/create-custom-sensitive-info-type-edm)

‎exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
applicable: Office 365 Security & Compliance Center
4+
title: New-DlpEdmSchema
5+
schema: 2.0.0
6+
author: chrisda
7+
ms.author: chrisda
8+
ms.reviewer:
9+
monikerRange: "o365scc-ps"
10+
---
11+
12+
# New-DlpEdmSchema
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the Office 365 Security & Compliance Center. For more information, see Office 365 Security & Compliance Center PowerShell (https://technet.microsoft.com/library/mt587091.aspx).
16+
17+
Use the New-DlpEdmSchema cmdlet to create exact data match (EDM) data loss prevention (DLP) schemas in the Security & Compliance Center.
18+
19+
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
20+
21+
## SYNTAX
22+
23+
```
24+
New-DlpEdmSchema [-FileData] <Byte[]> [-WhatIf] [-Confirm] [<CommonParameters>]
25+
```
26+
27+
## DESCRIPTION
28+
For an explanation and example of the EDM schema, see Define the schema for your database of sensitive information
29+
(https://docs.microsoft.com/office365/securitycompliance/create-custom-sensitive-info-type-edm#define-the-schema-for-your-database-of-sensitive-information).
30+
31+
You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in Office 365 Security & Compliance Center (https://go.microsoft.com/fwlink/p/?LinkId=511920).
32+
33+
## EXAMPLES
34+
35+
### -------------------------- Example 1 --------------------------
36+
```
37+
$edmSchemaXml = Get-Content "C:\My Documents\edm.xml" -Encoding Byte -ReadCount 0; New-DlpEdmSchema -FileData $edmSchemaXml -Confirm:$true
38+
```
39+
40+
This example creates a new DLP EDM schema. The first command reads the schema in the XML file to a variable, and the second command uses that information to create the DLP EDM schema.
41+
42+
## PARAMETERS
43+
44+
### -FileData
45+
The FileData parameter specifies the DLP EDM schema that you want to import.
46+
47+
A valid value for this parameter requires you to read the file to a byte-encoded object using the Get-Content cmdlet. For example, \(\[Byte\[\]\]\(Get-Content -Encoding Byte -Path "C:\\My Documents\\\<filename\>" -ReadCount 0\)\).
48+
49+
```yaml
50+
Type: Byte[]
51+
Parameter Sets: (All)
52+
Aliases:
53+
Applicable: Office 365 Security & Compliance Center
54+
Required: True
55+
Position: 0
56+
Default value: None
57+
Accept pipeline input: True (ByValue)
58+
Accept wildcard characters: False
59+
```
60+
61+
### -Confirm
62+
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
63+
64+
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
65+
66+
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
67+
68+
```yaml
69+
Type: SwitchParameter
70+
Parameter Sets: (All)
71+
Aliases: cf
72+
Applicable: Office 365 Security & Compliance Center
73+
Required: False
74+
Position: Named
75+
Default value: None
76+
Accept pipeline input: False
77+
Accept wildcard characters: False
78+
```
79+
80+
### -WhatIf
81+
The WhatIf switch doesn't work in the Office 365 Security & Compliance Center.
82+
83+
```yaml
84+
Type: SwitchParameter
85+
Parameter Sets: (All)
86+
Aliases: wi
87+
Applicable: Office 365 Security & Compliance Center
88+
Required: False
89+
Position: Named
90+
Default value: None
91+
Accept pipeline input: False
92+
Accept wildcard characters: False
93+
```
94+
95+
### CommonParameters
96+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
97+
98+
## INPUTS
99+
100+
###
101+
102+
## OUTPUTS
103+
104+
###
105+
106+
## NOTES
107+
108+
## RELATED LINKS
109+
110+
[Online Version](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/New-DlpEdmSchema)
111+
112+
[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/office365/securitycompliance/create-custom-sensitive-info-type-edm)

‎exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,4 +107,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
107107
108108
## RELATED LINKS
109109
110-
[Online Version](https://technet.microsoft.com/library/6a581c6b-e3ac-4c56-ada8-4e66c8891def.aspx)
110+
[Online Version](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage)
111+
112+
[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/office365/securitycompliance/create-custom-sensitive-info-type-edm)

‎exchange/exchange-ps/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
applicable: Office 365 Security & Compliance Center
4+
title: Remove-DlpEdmSchema
5+
schema: 2.0.0
6+
author: chrisda
7+
ms.author: chrisda
8+
ms.reviewer:
9+
monikerRange: "o365scc-ps"
10+
---
11+
12+
# Remove-DlpEdmSchema
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the Office 365 Security & Compliance Center. For more information, see Office 365 Security & Compliance Center PowerShell (https://technet.microsoft.com/library/mt587091.aspx).
16+
17+
Use the Remove-DlpEdmSchema cmdlet to remove exact data match (EDM) data loss prevention (DLP) schemas from the Security & Compliance Center.
18+
19+
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
20+
21+
## SYNTAX
22+
23+
```
24+
Remove-DlpEdmSchema [-Identity] <EdmStorageIdParameter> [-WhatIf] [-Confirm] [<CommonParameters>]
25+
```
26+
27+
## DESCRIPTION
28+
You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in Office 365 Security & Compliance Center (https://go.microsoft.com/fwlink/p/?LinkId=511920).
29+
30+
## EXAMPLES
31+
32+
### -------------------------- Example 1 --------------------------
33+
```
34+
Remove-DlpEdmSchema -Identity "Schema for Patient Records"
35+
```
36+
37+
This example removes the DLP EDM schema named Schema for Patient Records.
38+
39+
## PARAMETERS
40+
41+
### -Identity
42+
The Identity parameter specifies the DLP EDM schema that you want to remove. You can use any value that uniquely identifies the schema. For example:
43+
44+
- Name
45+
46+
- Distinguished name (DN)
47+
48+
```yaml
49+
Type: EdmStorageIdParameter
50+
Parameter Sets: (All)
51+
Aliases:
52+
Applicable: Office 365 Security & Compliance Center
53+
Required: True
54+
Position: 0
55+
Default value: None
56+
Accept pipeline input: True (ByPropertyName, ByValue)
57+
Accept wildcard characters: False
58+
```
59+
60+
### -Confirm
61+
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
62+
63+
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
64+
65+
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
66+
67+
```yaml
68+
Type: SwitchParameter
69+
Parameter Sets: (All)
70+
Aliases: cf
71+
Applicable: Office 365 Security & Compliance Center
72+
Required: False
73+
Position: Named
74+
Default value: None
75+
Accept pipeline input: False
76+
Accept wildcard characters: False
77+
```
78+
79+
### -WhatIf
80+
The WhatIf switch doesn't work in the Office 365 Security & Compliance Center.
81+
82+
```yaml
83+
Type: SwitchParameter
84+
Parameter Sets: (All)
85+
Aliases: wi
86+
Applicable: Office 365 Security & Compliance Center
87+
Required: False
88+
Position: Named
89+
Default value: None
90+
Accept pipeline input: False
91+
Accept wildcard characters: False
92+
```
93+
94+
### CommonParameters
95+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
96+
97+
## INPUTS
98+
99+
###
100+
101+
## OUTPUTS
102+
103+
###
104+
105+
## NOTES
106+
107+
## RELATED LINKS
108+
109+
[Online Version](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema)
110+
111+
[Create custom sensitive information types with Exact Data Match based classification](https://docs.microsoft.com/office365/securitycompliance/create-custom-sensitive-info-type-edm)

0 commit comments

Comments
 (0)