Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 795
Reply with quote  #1 
I had an issue with a customer, mail flow stopped, big fuss, lots of mails lost, issues and trouble. usual burning of Rome stuff.

Anyway, I've been trying to find out what happened, and in the process we have 2 users in on premise AD that were created in the last 4 months solely for the migration, an admin account and a user account.
Using Azure AD Connect to sync to Azure AD/ Office 365.
One of the teat users was an on premise mailbox user, migrated to O365 mailbox and then the license was taken away from them. (so no mailbox) Except they are listed now as a contact in O365 Exchange ECP Contacts, but not in Azure AD/ Office 365 Contacts list.
They are listed in unlicensed users on Azure AD/ Office 365 Users

Looking at their AD Attributes the users are listed as mailbox users as per https://blogs.technet.microsoft.com/johnbai/2013/09/11/o365-exchange-and-ad-how-msexchrecipientdisplaytype-and-msexchangerecipienttypedetails-relate-to-your-on-premises/

If I move the users to a non O365 sync'd OU the Azure AD/ O365 user account and the contact disappear.

Why is this a problem....when we attempt to send a mail to the non existent user mailbox, rather than get an NDR we are getting a mail routing loop from which the mail expires due to too many hops (the apparent issue we had on Tuesday 28th going into early 29th)
But this issue was not there over 3 weeks ago.

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
jsclmedave

Administrator
Registered:
Posts: 441
Reply with quote  #2 
Is this a feature so that you cannot attempt to harvest Email Accounts..?   So that you dont know what is bogus (NDR) and what actually went through..?
__________________
Tim Bolton @jsclmedave
Email: [string](0..20|%{[char][int](32+('527377347976847978324785847679797514357977').substring(($_*2),2))}) -replace ' '  

New to the forum? Please Read this
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 795
Reply with quote  #3 
No.
This is some other attribute that is telling Exchange online that the mailbox user msExchangeDisplayType is a mailbox user, yet it has them in as a contact.

By right if this was a feature I'd have it for at least 30 other users whose licenses have been removed.

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.