Added a new domain to our Office 365 instance through the admin portal, setup all DNS records and verified/activated. However, during this process we found that one of our technicians had previously created an Office 365 trial with this domain, so we had to sign-in to that portal and remove the domain there before it would verify in our new Office 365 instance.
However, this domain is not showing in Acceptable Domains under mail routing for some reason, all the rest of our vanity domains are. If I try to create a new user or shared mailbox, I cannot add an email address with this domain either.
I'm assuming it's because of this why we cannot set a user's primary SMTP address to this new domain and authenticate as well. (if we set it, we get errors getting into OWA and Outlook). We use OneLogin as our SSO provider, but they've been unable to find any issues with the setup....really thinking this is due to the new domain not being completely "added" to our Office 365 instance.
Looking around I saw this community post: http://community.office365.com/en-us/forums/148/t/156101.aspx?PageIndex=6
The OP's last comment states he had to have Microsoft remove the old tenant on the backend in order for this to get resolved. Has anyone had any experience with this?
I have a ticket in with Microsoft (SRX1216196223ID) this as well, but this is severely affecting our company as I cannot set a user's primary SMTP address to this new domain, so hoping someone can shed some light...or escalate this as my attempts have been futile.