Applies to: Exchange Server 2016

This cmdlet is available only in on-premises Exchange Server 2016.

The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. This cmdlet is only used for diagnostic purposes.

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

Reset-ProvisioningCache -Application <String> -GlobalCache <SwitchParameter> -Server <Fqdn> <COMMON PARAMETERS>
Reset-ProvisioningCache -Application <String> -Server <Fqdn> [-CurrentOrganization <SwitchParameter>] [-Organizations <MultiValuedProperty>] <COMMON PARAMETERS>
COMMON PARAMETERS: [-CacheKeys <MultiValuedProperty>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]

This example resets the provisioning cache for Windows PowerShell running on the server in an on-premises Exchange organization and specifies that all cache keys are cleared.

Reset-ProvisioningCache -Server -Application Powershell -GlobalCache

This example runs in a multi-tenant deployment by a data center administrator to reset the provisioning cache for Windows PowerShell for the tenant and clear all cache keys.

Reset-ProvisioningCache -Application Powershell-Proxy -Server -GlobalCache

The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators need to run this cmdlet only if incorrect links or properties are stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache. This is a rare occurrence because the provisioning cache has invalidation notification logic.

The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don't change for months or years after they're created, they're stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance.

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 "Exchange server configuration settings" entry in the Exchange infrastructure and PowerShell permissions topic.


Parameter Required Type Description




The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values:

  • Powershell

  • Powershell-LiveId

  • Powershell-Proxy

  • PowershellLiveId-Proxy

  • Ecp

  • Psws




The GlobalCache switch specifies that all cache keys are cleared.




The Server parameter specifies the fully qualified domain name (FQDN) of the server that the application you want to reset is running on.




The CacheKeys parameter specifies the value for the cache key that you want to clear. The format for the values should contain 32 digits separated by four dashes: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Use the Dump-ProvisioningCache cmdlet to return a list of cache keys.




The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.

  • Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.




The CurrentOrganization switch specifies that the provision cache is reset for this organization.




The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments.




The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this 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.