This works fine running it in a powershell session outside of PSU. When I run it using PSU I get the error: Error creating contact: No provisioning handler is installed.
Without knowing how your PSU is setup, it’s probably a permission issue. What is the account you are using to run your PSU instance or the PSU environment? Does that account have proper permissions in Exchange? It will use ‘Local System’ by default which obviously won’t have any permissions in Exchange.
As a side note, while it does work for most cmdlets, it’s not recommended to manually load the Exchange Snap-ins for anything other than Exchange 2010 and if you are still running Exchange 2010 then you have a bunch of other problems. You should always do a remote connection to an actual Exchange server instead of a server with mgmt tools installed on it.
The service account that PSU runs under is an account operator and Exchange Organization Administrators in AD. It’s also has the roles of Organization Management and Mail Recipient Creation in exchange.
We recently updated the ad scheme to exchange se and we’re shutting down the actual exchange server since it’s only for editing a few mail-related objects. the idea was to install the tools on another server to be able to create scripts to do what the UI would do before.