Warning: Undefined array key "is_rate_editable" in /home/vhosts/itexperience.net/httpdocs/wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php on line 1303 FIX: This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox - itexperience.net
Skip to content
FIX: This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox
When I tried to make a Office 365 Exchange Online mailbox visible in my on-premises environment, the following error occurred:
PS C:\Windows\System32\WindowsPowerShell\v1.0> Enable-RemoteMailbox user1 -RemoteRoutingAddress user1@tenant.mail.onmicrosoft.com -PrimarySmtpAddress user1@tenant.com This task does not support recipients of this type. The specified recipient Int.tenant.com/Users/user1 is of type RemoteUserMailbox. Please make sure that this recipient matches the required recipient type for this task.
This task does not support recipients of this type. The specified recipient is of type RemoteUserMailbox
I wanted to use the Enable-RemoteMailbox cmdlet to mail-enable the user in my Exchange 2013 environment. The issue started weeks ago when a user complained he could not use Outlook on his pc. He could use Outlook WebApp though. I then found out our Servicedesk created his mailbox in Office365 using the Office 365 portal. In a hybrid environment, you still have to run the Enable-RemoteMailbox command to mail-enable the user on-premises. After running Enable-RemoteMailbox the user was able to use Outlook.
Funny part of the This task does not support recipients of this type. The specified recipient Int.tenant.com/Users/user1 is of type RemoteUserMailbox. error: the user had no issue and was already enabled and visible in my Exchange 2013 exchange control panel. My bad… :’-)
It was already enabled but just needed some time. I guess some sync in the background.
It’s probably too long ago for me to remember the exact issue and solution. Sorry about that.
Check that the user has been licenced for Exchange
Check that the mailbox has actually appeared in Exchange Online
There are a number of causes but you need to troubleshoot your tenant and then contact MS if you are still having issues
Mordenthral
4 years ago
I had this issue. I found that the username and email address were not the same. Username was, for instance, user.name and the email was name.user (both the primary and remote routing addresses). I un-ticked the auto-generation mail policy, modified the email addresses, saved, then added the backwards mail address as an alias so it would keep working. I then forced a synch from the AAD Connect server.
Kevin
3 years ago
This will also occur if the remote mailbox has already been provisioned but the user hasn’t been licenced yet
Buuuuuuuut how did you fix it? You say “After running Enable-RemoteMailbox…”, but the problem is you can’t run Enable-RemoteMailbox…
It was already enabled but just needed some time. I guess some sync in the background.
It’s probably too long ago for me to remember the exact issue and solution. Sorry about that.
Check that the user has been licenced for Exchange
Check that the mailbox has actually appeared in Exchange Online
There are a number of causes but you need to troubleshoot your tenant and then contact MS if you are still having issues
I had this issue. I found that the username and email address were not the same. Username was, for instance, user.name and the email was name.user (both the primary and remote routing addresses). I un-ticked the auto-generation mail policy, modified the email addresses, saved, then added the backwards mail address as an alias so it would keep working. I then forced a synch from the AAD Connect server.
This will also occur if the remote mailbox has already been provisioned but the user hasn’t been licenced yet