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
Copy file name to clipboardExpand all lines: defender-office-365/mdo-support-teams-about.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ If you'd rather use [Exchange Online PowerShell](/powershell/exchange/connect-to
83
83
- There's only one Teams protection policy in an organization. By default, that policy is named Teams Protection Policy.
84
84
- Using the **New-TeamsProtectionPolicy** cmdlet is meaningful only if there's no Teams protection policy in the organization (the **Get-TeamsProtectionPolicy** cmdlet returns nothing). You can run the cmdlet without error, but no new Teams protection policies are created if one already exists.
85
85
- You can't remove an existing Teams protection policy or Teams protection policy rule (there's no **Remove-TeamsProtectionPolicy** or **Remove-TeamsProtectionPolicyRule** cmdlet).
86
-
- By default, there's no Teams protection policy rule (the **Get-TeamsProtectionPolicyRule** cmdlet returns nothing). Specifying quarantine policies or exceptions for ZAP for Teams in the Defender portal creates the rule automatically. Or, you can use the **New-TeamsProtectionPolicyRule** cmdlet to create the rule in PowerShell if it doesn't already exist.
86
+
- By default, there's a Teams protection policy rule named Teams Protection Policy Rule in an organization as returned by the **Get-TeamsProtectionPolicyRule** cmdlet. You can use the Defender portal or the **Set-TeamsProtectionPolicyRule** cmdlet to modify the quarantine policies or exceptions for ZAP for Teams.
87
87
88
88
#### Use PowerShell to view the Teams protection policy and Teams protection policy rule
0 commit comments