Merge branch 'main' into QuarAS-chrisda

Author: chrisda

exchange/exchange-ps/exchange/Get-Group.md

@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
 
-Use the Get-Group cmdlet to view existing group objects in your organization. This cmdlet returns security groups, mail-enabled security groups, distribution groups, and role groups.
+Use the Get-Group cmdlet to view existing group objects in your organization. In all environments, this cmdlet returns mail-enabled security groups, distribution groups, role groups, and room lists. For details about other supported group types in on-premises Exchange environments, see the RecipientTypeDetails parameter description.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

teams/teams-ps/teams/Get-CsOnlineUser.md

@@ -29,6 +29,7 @@ Get-CsOnlineUser [[-Identity] <UserIdParameter>]
  [-OU <OUIdParameter>]
  [-ResultSize <Unlimited>]
  [-SkipUserPolicies]
+ [-SoftDeletedUser]
  [-Sort]
  [-UnassignedUser]
  [-UsePreferredDC]
@@ -494,6 +495,23 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -SoftDeletedUser
+
+This parameter enables you to return a collection of all the users who are deleted and can be restored within 30 days from their deletion time
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -Sort
 
 Sorting will now be enabled in Teams PowerShell Module 5.9.0 and later by using the "-Sort" or "-OrderBy" parameters in GCC High and DoD environments. These updates will be applicable to older Teams PowerShell versions starting from 15th March 2024 in GCC High and DoD environments(note that this parameter is already rolled out in commercial environments). For example:
@@ -506,7 +524,7 @@ Sorting will now be enabled in Teams PowerShell Module 5.9.0 and later by using
 ```yaml
 Type: String
 Parameter Sets: (All)
-Aliases:
+Aliases: OrderBy
 Applicable: Microsoft Teams
 
 Required: False

teams/teams-ps/teams/New-CsTeamsEmergencyCallingPolicy.md

@@ -27,20 +27,37 @@ This cmdlet creates a new Teams Emergency Calling policy. Emergency calling poli
 
 ## EXAMPLES
 
-### Example 1
+### Emergency calling policy Example 1
+In the following example, ECP1, an emergency calling policy with identify ECP1 is configured with full security desk configuration. Extended notifications for the test emergency number, 933, are set to null.
+**ECP1**
+<ul>
+    <li>Notification group: [email protected]</li>
+    <li>Notification Dial Out Number - 14255551234</li>
+    <li>Notification Mode - Conferenced in and are unmuted</li>
+    <li>External Lookup Mode - On</li>
+</ul>
+
 ```powershell
-New-CsTeamsEmergencyCallingPolicy -Identity TestECP -Description "Test ECP" -NotificationGroup "[email protected]" -NotificationDialOutNumber "+14255551234" -NotificationMode NotificationOnly -ExternalLocationLookupMode Enabled
+$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933"
+New-CsTeamsEmergencyCallingPolicy -Identity ECP1 -Description "Test ECP1" -NotificationGroup "[email protected]" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted -ExternalLocationLookupMode Enabled -ExtendedNotifications @{add=$en1}
 ```
 
-This example creates a Teams Emergency Calling policy that has an identity of TestECP, where a notification group and number is being defined, the external location lookup mode is enabled and also the type of notification.
+### Emergency calling policy Example 2
+In the following example, ECP2, an emergency calling policy with identify ECP2 is configured with both 911 and 933 in the extended notification settings. Extended notifications for the test emergency number 911 are set to notify two groups separated by ";" and for 933 are set to null.
+**ECP2**
+<ul>
+    <li>Notification group: null</li>
+    <li>Notification Dial Out Number - null</li>
+    <li>Notification Mode - null</li>
+    <li>External Lookup Mode - On</li>
+</ul>
 
-### Example 2
 ```powershell
-New-CsTeamsEmergencyCallingPolicy -Identity "TestECP2" -NotificationGroup "[email protected];[email protected]"
+$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "[email protected];[email protected]" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted
+$en2 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933"
+New-CsTeamsEmergencyCallingPolicy -Identity ECP2 -Description "Test ECP2" -ExternalLocationLookupMode Enabled -ExtendedNotifications @{add=$en1,$en2}
 ```
 
-This example creates a Teams Emergency Calling policy that has an identity of TestECP2, with default settings, except for the Notification Group. This parameter expects a single string with all users and groups separated by ";".
-
 ## PARAMETERS
 
 ### -Identity
@@ -90,8 +107,6 @@ Accept wildcard characters: False
 
 ### -ExtendedNotifications
 
-**Note**: The use of extended notifications and this parameter is currently not supported.
-
 A list of one or more instances of TeamsEmergencyCallingExtendedNotification. Each TeamsEmergencyCallingExtendedNotification should use a unique EmergencyDialString.
 
 If an extended notification is found for an emergency phone number based on the EmergencyDialString parameter the extended notification will be controlling the notification. If no extended notification is found the notification settings on the policy instance itself will be used.

teams/teams-ps/teams/Set-CsTeamsEmergencyCallingPolicy.md

@@ -34,7 +34,24 @@ This cmdlet modifies an existing Teams Emergency Calling policy. Emergency calli
 Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -NotificationGroup "[email protected];[email protected]"
 ```
 
-This example modifies an existing policy instance with identity TestECP.
+This example modifies NotificationGroup of an existing policy instance with identity TestECP.
+
+### Example 2
+```powershell
+$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "[email protected]" -NotificationMode ConferenceUnMuted
+Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -ExtendedNotifications @{remove=$en1}
+```
+
+This example first creates a new Teams Emergency Calling Extended Notification object and then removes that Teams Emergency Calling Extended Notification from an existing Teams Emergency Calling policy.
+
+### Example 3
+```powershell
+$en1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "[email protected]" -NotificationDialOutNumber "+14255551234" -NotificationMode ConferenceUnMuted
+$en2 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "933"
+Set-CsTeamsEmergencyCallingPolicy -Identity "TestECP" -ExtendedNotifications @{add=$en1,$en2}
+```
+
+This example first creates two new Teams Emergency Calling Extended Notification objects and then adds them to an existing Teams Emergency Calling policy with identity TestECP.
 
 ## PARAMETERS