Thursday, 14 September 2017 13:17

The Case of Existing Email Address

Written by
Rate this item
(1 Vote)

image

This case is my favorite kind of case, one where I get to learn something new to solve a problem. The other day I was creating a couple of users in my Office 365 environment and assigning Exchange Online licenses when I was interrupted with a message that informed me that "The email address "This email address is being protected from spambots. You need JavaScript enabled to view it." is already being used by contact (Christopher Blair) This email address is being protected from spambots. You need JavaScript enabled to view it.. Use a different email address.".

The cause appears to be relatively straight forward: this issue may occur if the user name is already used or if an existing email address that's based on the user name already exists. In this case licensing attempt will fail if the provisioning process determines that another object already has a user name or an email address that matches the user name that's being created.

I verified the issue, checked existing users and email aliases, but could not find anything that would explain the problem - none of existing users were using the mail address This email address is being protected from spambots. You need JavaScript enabled to view it..

Next, I connected to Exchange Online by using a remote Windows PowerShell session ...

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session

... and ran following command:

$DuplicateUser = "This email address is being protected from spambots. You need JavaScript enabled to view it."
Get-Mailbox | where {$_.EmailAddresses -match $DuplicateUser} | fl Name, RecipientType, EmailAddresses

Unfortunately, the command returned no results, dashing my hopes for quickly finding a clue, so I turned to TechNet forums for help. As a reader of this blog I suspect that you, like me, are a frequent visitor to TechNet forums. I have spent dozens of hours helping other people out, but this time it was my turn to ask for help. Within minutes, I received a recommendation to run a number of commands against Exchange Online / Azure AD. The key to solving the mystery lay in executing Get-Recipient cmdlet, which allows you to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups):

Get-Recipient -ResultSize Unlimited | where {$_.EmailAddresses -match "$DuplicateUser"}

Name RecipientType
---- -------------
Christopher Blair MailContact

It would seem that I had a contact in my address book with the exactly same proxy address as the user object I was trying to create. Confident I solved my mystery, I logged into the Exchange admin center, navigated to receipients / contacts tab and removed the contact object associated with the proxy address. I tried to create the user again and to my immense satisfaction, the provisioning process finished within a couple seconds. The case was closed! As to why the proxy address was already present in the contacts list, I can only assume that at some point I provisioned that user and then either changed user name or deleted the user object, but forgot to update or delete the contact.

Read 2718 times Last modified on Friday, 15 September 2017 23:41
  1. Comments (0)

  2. Add yours
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
0 Characters
Attachments (0 / 3)
Share Your Location

Recent Posts

  • An alternative ESU MAK Activation Solution
    This blog post was shared with me by a colleague of mine, Daniel Dorner, a Microsoft Premier Field Engineer. It’s…
    Written on Wednesday, 04 December 2019 21:04
  • The Case of Missing UE-V Templates
    My customers often deal with unexpected Windows behavior and this case is no different. This particular one is especially interesting…
    Written on Tuesday, 03 September 2019 12:20
  • The Case of Corrupted Store Apps
    A few days ago I began experiencing issues with built-in Windows apps where various apps would flash open and close…
    Written on Wednesday, 14 August 2019 13:36
  • The Case of Changing Default Printer
    While I sometimes long for the day when I no longer have to deal with unexpected Windows 10 behavior, there’s…
    Written on Wednesday, 14 August 2019 20:36
  • Windows 10 1903: Useful Resources for IT Professionals
    Windows 10, version 1903 is now available via Windows Update for Business, Windows Server Update Services (WSUS) and the Volume…
    Written on Friday, 07 June 2019 11:21
  • Windows 10 1903 Built-In Apps: What to Keep
    The development of the Windows 10, version 1903 is finished and the update is now available for download from Visual…
    Written on Monday, 03 June 2019 06:59