From f00ec9c1d37f36b9569003b1a6a0e261b7766ab4 Mon Sep 17 00:00:00 2001 From: rnicolson Date: Fri, 15 Sep 2023 11:20:04 -0500 Subject: [PATCH] Update Set-CMCollectionCloudSync.md Adds a note about a current limitation in the cmdlet. This was confirmed by Microsoft support in a premier support case. If you would like additional details please reach out for the case number. --- sccm-ps/ConfigurationManager/Set-CMCollectionCloudSync.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/sccm-ps/ConfigurationManager/Set-CMCollectionCloudSync.md b/sccm-ps/ConfigurationManager/Set-CMCollectionCloudSync.md index d93754dc..29d12c52 100644 --- a/sccm-ps/ConfigurationManager/Set-CMCollectionCloudSync.md +++ b/sccm-ps/ConfigurationManager/Set-CMCollectionCloudSync.md @@ -44,6 +44,12 @@ Use this cmdlet to configure collection membership synchronization to Azure Acti > [!NOTE] > Run Configuration Manager cmdlets from the Configuration Manager site drive, for example `PS XYZ:\>`. For more information, see [getting started](/powershell/sccm/overview). +> +> [!NOTE] +> There is currently a limitation with this cmdlet where the -AddGroupName and -RemoveGrouName parameters are limited in the number of groups it searches in the tenant. +> It is equivilent to running "Get-AzureADGroup -top 900" and then searching the results for the group name. If the group is not in the returned results you will see +> an error "Set-CMCollectionCloudSync : The specified group discovery scope 'GroupName' could not be found." There is currently no way to filter or sort the results to +> ensure your group is returned in the object. ## EXAMPLES