Merge pull request MicrosoftDocs#10555 from isrumnon/patch-32

Update Get-CsOnlineUser.md

Author: tiburd

skype/skype-ps/skype/Get-CsOnlineUser.md

@@ -142,7 +142,7 @@ Accept wildcard characters: False
 ### -Identity
 Indicates the Identity of the user account to be retrieved.
 
-For TeamsOnly customers using the Teams PowerShell Module version 3.0.0 or later, you use the following values to identify the account (note that these changes are only rolled out in commercial environments at present and will be applicable to the lastest TPM versions in government environments starting March 31, 2023.):
+For TeamsOnly customers using the Teams PowerShell Module version 3.0.0 or later, you use the following values to identify the account (note that these changes are only rolled out in commercial environments including GCC at present, and will be applicable to the latest TPM versions in GCC High and DoD environments starting March 15, 2023 with TPM 5.0.1):
 
 - GUID
 - SIP address
@@ -253,8 +253,8 @@ These filtering operators have been reintroduced:
 - “-like” operator now supports the use of wildcard operators in ‘contains’ and ‘ends with’ scenarios. For example:
 
 ```
-Contains Scenario: Get-CsOnlineUser  -Filter "AssignedPlan -like '*MCO*'"
-Ends with scenario: Get-CsOnlineUser  -Filter {AssignedPlan -like '*MCO'}
+Contains Scenario: Get-CsOnlineUser  -Filter "DisplayName -like '*abc*'"
+Ends with scenario: Get-CsOnlineUser  -Filter {DisplayName -like '*abc'}
 ```
 - “-contains” can now be used to filter properties that are an array of strings like FeatureTypes, ProxyAddresses, and ShadowProxyAddresses. For example:
 ```
@@ -269,10 +269,11 @@ Get-CsOnlineUser -Filter {UserPrincipalName -gt/-le/-lt “abc”}
 ```
 Get-CsOnlineUser -Filter {ExternalAccessPolicy -ge "xyz_policy"}
 ```
+**Updates in Teams PowerShell Module version 3.0.0 and above**
 
 The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 3.0.0 and later (excluding updates mentioned previously for Teams PowerShell Module version 5.0.0):
 
-In the Teams PowerShell Module version 3.0.0 or later, filtering functionality is now limited to the following attributes (note that these changes are only rolled out in commercial environments at present and will be applicable to the lastest TPM versions in government environments starting March 31, 2023.):
+In the Teams PowerShell Module version 3.0.0 or later, filtering functionality is now limited to the following attributes (note that these changes are only rolled out in commercial environments including GCC at present, and will be applicable to the latest TPM versions in GCC High and DoD environments starting March 15, 2023 with TPM 5.0.1):
 
 - AccountType
 - AccountEnabled
@@ -546,12 +547,22 @@ New attributes have now been introduced in the output of Get-CsOnlineUser when n
 - UserValidationErrors                   
 - WhenCreated    
 
-Unlicensed Users: Unlicensed users would show up in the output for 30 days post-license removal.
-Soft deleted users: These users will be displayed in the output of Get-CsOnlineUser and the TAC Manage Users page by default with SoftDeletionTimestamp set to a value.
+The following updates are now applicable to the output in scenarios where "-identity" parameter is not used:
+
+- Only valid OnPrem users would be available in the output: These are users that are DirSyncEnabled and have a valid OnPremSipAddress or SIP address in ShadowProxyAddresses.
+- Guest users are now available in the output.
+- Unlicensed Users: Unlicensed users would show up in the output for 30 days post-license removal.
+- Soft deleted users: These users will be displayed in the output of Get-CsOnlineUser and the TAC Manage Users page by default with SoftDeletionTimestamp set to a value.
+
+If any information is required for a user that is not available in the output (when not using "-identity" parameter) then it can be obtained using the "-identity" parameter. Information for all users would be available using the "-identity" parameter until they are hard deleted.
+
+If Guest users and SoftDeletedUsers are not required in the output then they can be filtered out by using filter on AccountType and SoftDeletionTimestamp respectively. For example:
+- Get-CsOnlineUser -Filter {AccountType -ne 'Guest'}
+- Get-CsOnlineUser -Filter {SoftDeletionTimestamp -eq $null}
 
 **Updates in Teams PowerShell Module version 3.0.0 and above**
 
-The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 3.0.0 and later, excluding updates mentioned previously for Teams PowerShell Module version 5.0.0 (note that these changes are only rolled out in commercial environments at present and will be applicable to the lastest TPM versions in government environments starting March 31, 2023.):
+The following updates are applicable for organizations having TeamsOnly users that use Microsoft Teams PowerShell version 3.0.0 and later, excluding updates mentioned previously for Teams PowerShell Module version 5.0.0 (note that these changes are only rolled out in commercial environments including GCC at present and will be applicable to the latest TPM versions in GCC High and DoD environments starting March 15, 2023 with TPM 5.0.1):
 
 *New user attributes*: