From a2106842b253c4e1458fcd941dfe0b424ff05b5a Mon Sep 17 00:00:00 2001 From: Erik Kredatus Date: Mon, 3 Mar 2025 23:59:11 +0000 Subject: [PATCH 1/3] Removing Immersive events TPM Documentation --- .../teams-ps/teams/New-CsTeamsEventsPolicy.md | 19 ------------------- .../teams-ps/teams/Set-CsTeamsEventsPolicy.md | 18 ------------------ 2 files changed, 37 deletions(-) diff --git a/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md index 28e4dcb288..6276f82dc8 100644 --- a/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md +++ b/teams/teams-ps/teams/New-CsTeamsEventsPolicy.md @@ -19,7 +19,6 @@ New-CsTeamsEventsPolicy [-Identity] [-AllowWebinars ] [-AllowTo [-TownhallEventAttendeeAccess ] [-RecordingForTownhall ] [-RecordingForWebinar ] [-TranscriptionForTownhall ] [-TranscriptionForWebinar ] [-AllowEventIntegrations ] [-TownhallChatExperience ] [-UseMicrosoftECDN ] [-EventAccessType ] [-WhatIf] [-Confirm] [] -[-ImmersiveEvents ] ``` ## DESCRIPTION @@ -266,24 +265,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ImmersiveEvents -This setting governs if a user can create Immersive Events using Teams Events. -Possible values are: - - **Enabled**: Enables creating Immersive Events. - - **Disabled**: Disables creating Immersive Events. - -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: Enabled -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -AllowEventIntegrations This setting governs the access to the integrations tab in the event creation workflow. diff --git a/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md b/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md index 310c9a75e8..f9eebe43b6 100644 --- a/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md +++ b/teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md @@ -23,7 +23,6 @@ Set-CsTeamsEventsPolicy [-AllowWebinars ] [-EventAccessType ] [- [-TranscriptionForTownhall ] [-TranscriptionForWebinar ] [-UseMicrosoftECDN ] [-Identity] [-Force] [-WhatIf] [-Confirm] [] - [-ImmersiveEvents ] ``` ## DESCRIPTION @@ -389,23 +388,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -ImmersiveEvents -This setting governs if a user can create Immersive Events using Teams Events. -Possible values are: - - **Enabled**: Enables creating Immersive Events. - - **Disabled**: Disables creating Immersive Events. -```yaml -Type: String -Parameter Sets: (All) -Aliases: - -Required: False -Position: Named -Default value: Enabled -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Confirm The Confirm switch does not work with this cmdlet. From 994dc9c8694a7f05cc39c8fefd7c07c9a6bfdebe Mon Sep 17 00:00:00 2001 From: Ben Jenkins <140325164+Yebbenbe@users.noreply.github.com> Date: Tue, 4 Mar 2025 11:46:04 -0400 Subject: [PATCH 2/3] add info re: licensing as this appears to not function with P2. Have been trying to add a user to Quarantine Release notifs - but have unfortunately learned that Set doesn't work on Defaults, and New only works with Enterprise. So that's a bummmer. --- exchange/exchange-ps/exchange/New-ProtectionAlert.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/exchange/exchange-ps/exchange/New-ProtectionAlert.md b/exchange/exchange-ps/exchange/New-ProtectionAlert.md index 91713c3de6..788a0992bb 100644 --- a/exchange/exchange-ps/exchange/New-ProtectionAlert.md +++ b/exchange/exchange-ps/exchange/New-ProtectionAlert.md @@ -16,6 +16,8 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the New-ProtectionAlert cmdlet to create alert policies in the Microsoft Purview compliance portal. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries in the Microsoft Purview compliance portal. +This cmdlet will not work without Enterprise licenses (including P2) - input will be accepted, but it will return that an Enterprise license is required. Because Default alert policies cannot be edited with PowerShell, Alert Policies cannot be managed by PowerShell with P1/P2 licenses - [only Enterprise/Government licenses](https://learn.microsoft.com/en-us/purview/alert-policies) + For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). ## SYNTAX From 1f58b9ed52da00b6c91ca0254fb917b09d00baa3 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 4 Mar 2025 09:27:48 -0800 Subject: [PATCH 3/3] Update New-ProtectionAlert cmdlet documentation --- exchange/exchange-ps/exchange/New-ProtectionAlert.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/exchange/exchange-ps/exchange/New-ProtectionAlert.md b/exchange/exchange-ps/exchange/New-ProtectionAlert.md index 788a0992bb..486b45298e 100644 --- a/exchange/exchange-ps/exchange/New-ProtectionAlert.md +++ b/exchange/exchange-ps/exchange/New-ProtectionAlert.md @@ -14,9 +14,15 @@ ms.reviewer: ## SYNOPSIS This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). -Use the New-ProtectionAlert cmdlet to create alert policies in the Microsoft Purview compliance portal. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries in the Microsoft Purview compliance portal. - -This cmdlet will not work without Enterprise licenses (including P2) - input will be accepted, but it will return that an Enterprise license is required. Because Default alert policies cannot be edited with PowerShell, Alert Policies cannot be managed by PowerShell with P1/P2 licenses - [only Enterprise/Government licenses](https://learn.microsoft.com/en-us/purview/alert-policies) +Use the New-ProtectionAlert cmdlet to create alert policies in the Microsoft Purview compliance portal and the Microsoft Defender portal. Alert policies contain conditions that define the user activities to monitor, and the notification options for email alerts and entries. + +> [!NOTE] +> Although the cmdlet is available, you receive the following error if you don't have an enterprise license: +> +> _Creating advanced alert policies requires an Office 365 E5 subscription or Office 365 E3 subscription with an Office 365 Threat Intelligence or +Office 365 EquivioAnalytics add-on subscription for your organization. With your current subscription, only single event alerts can be created._ +> +> For more information, see [Alert policies in Microsoft 365](https://learn.microsoft.com/purview/alert-policies). For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).