Set-NectarMSTeamsPartialMonitoringLimit

Configure a limit to the number of users that are monitored in Nectar DXP

Description

Configure a limit to the number of users that are monitored in Nectar DXP. Uses membership in a specified Azure AD group to determine the users we pull call records.
Requires a global admin account. Not available to tenant-level admins.

Syntax

Set-NectarMSTeamsPartialMonitoringLimit
  -MaxUsers  <Int32>
  -GroupName  <String>
  -Enabled  <Boolean>
  -SkipValidation
  -TenantName  <String>

Examples

Example 1

Set-NectarMSTeamsUserMonitoringLimit -MaxUsers 1000 -GroupName N10Users -TenantName contoso

Sets the maximum number of monitored users on the Contoso tenant to 1000 and uses the members of the N10Users group as the list of users to be monitored

Parameters

-MaxUsers <Int32>
The maximum number of users that will be monitored. Any group members above MaxUsers will not be monitored.

Parameter	Value
Required	true
Position	1
Required	true
Default Value	0
Accept pipeline input?	true (ByPropertyName)
Accept wildcard characters?	false

-GroupName <String>
The display name of the group that contains the users who will be monitored. If the group contains spaces, enclose the name in quotes

Parameter	Value
Required	false
Position	2
Required	false
Default Value	None
Accept pipeline input?	true (ByPropertyName)
Accept wildcard characters?	false

-Enabled <Boolean>

Parameter	Value
Required	false
Position	3
Required	false
Default Value	True
Accept pipeline input?	false
Accept wildcard characters?	false

-SkipValidation <SwitchParameter>
Does not attempt to validate the existence of the Azure AD group before enabling. Use with caution.

Parameter	Value
Required	false
Position	named
Required	false
Default Value	False
Accept pipeline input?	false
Accept wildcard characters?	false

-TenantName <String>
The name of the Nectar DXP tenant. Used in multi-tenant configurations.