Applies to: Exchange Server 2013

This topic no longer applies to the cloud-based service. It applies only to on-premises Exchange 2013. To see the current version of the topic that applies to the cloud-based service, change the (v=exchg.150) value in the URL to (v=exchg.160).

Use the Remove-UMHuntGroup cmdlet to remove and delete an existing Unified Messaging (UM) hunt group.

For information about the parameter sets in the Syntax section below, see Syntax.

Remove-UMHuntGroup -Identity <UMHuntGroupIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

This example deletes the UM hunt group MyUMHuntGroup.

Remove-UMHuntGroup -Identity MyUMHuntGroup

The Remove-UMHuntGroup cmdlet deletes an existing UM hunt group from Active Directory. When the Remove-UMHuntGroup cmdlet is used, the UM hunt group is removed from the UM IP gateway, and then deleted from Active Directory. If the operation leaves the UM IP gateway without any remaining configured UM hunt groups, the IP gateway can't handle or process Unified Messaging calls.

After this task is completed, the UM hunt group is removed from Active Directory.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "UM hunt groups" entry in the Unified Messaging permissions topic.


Parameter Required Type Description




The Identity parameter specifies the identifier for the UM hunt group being deleted. This is the directory object ID for the UM hunt group object.




The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.




This parameter is available only in on-premises Exchange 2013.

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.




The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.