This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I need help troubleshooting an issue with syncing proxyaddresses from Active Directory to Entra ID. Our organization (company-a.com) has recently acquired another company with a different domain (company-b.com), and we are in the process of migrating their email to our Exchange Online organization. The email migration is not yet complete, so their domain (company-b.com) is currently set as an internal relay in the Exchange Online organization of company-a.com. The domain has been verified in the company-a.com M365 tenant via TXT record. Additionally, company-b.com has been added to the Active Directory domain of company-a.com as a UPN suffix (not as a separate domain).
I have a single test user with an email address in our primary domain, and I've added a proxy address to that user for the acquired domain in Active Directory. However, when I force a delta sync to Entra ID, the proxyaddresses using the company-b.com domain are not syncing, and I'm seeing an error message (below). I've reviewed relevant documentation, but the problem persists. Can anyone help me figure out why the proxyaddresses are not syncing?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Ian Brown,
Please kindly understand the Exchange Online tag here we mainly focus on general issues about Exchange Online, looks like your issue is more related to Entra ID. In order to better solve your problem, we will add "Microsoft Entra ID" tag for you.
Thanks for your understanding.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
@Ian Brown Thank you for reaching out to us, above mentioned issue needs to worked upon by multiple teams (Exchange online & Entra ID ), would recommend to open a support ticket if you have a support contract with us else share the Azure Subscription id where we can enable the one time support option for you to fix the above mentioned issue.
Please send us an email on azcommunity [at] microsoft [dot] com referencing this issue with a subject line "ATTN:Givary" along with your Azure subscription id and we will help you with support options on this.
Hello Givary,
This issue is now resolved. It appears to have just been some kind of delay in the forward provisioning of the accepted domain in Exchange Online.
