Issue a X500 address is automatically added to the proxyAddresses

Question

Accounts (without Exchange Online mailboxes) are also receiving this X500 address, which interferes with proper propagation of the mail attribute to Entra ID. We no longer have an on-prem Exchange environment, but Exchange attributes are still present in AD. How can we solve this?

Comments

Hello,

Sorry for the confusion, but we are not sure what the issue is. Please describe the behavior you are facing in all possible details, with screenshots and live examples. You can post screenshots here or send them to us at support@adaxes.com.

---

When we create a new AD user with Adaxes the AD attribute proxyAddresses gets the value x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=537c08e656a44b8b83a332e3a19bb72c-5589e6be-e4

Even though the AD mail attribute is filled in with a valid (external) email address.

After syncing with Entra, the Proxy Address in Entra becomes:

And this will then be the email address in Entra instead of the correct email address

Now we correct this manually by putting the correct email address as SMTP: address in the AD Proxy Address and performing a new Entra sync.

How can we prevent this issue or fix it so it corrects automatically?

---

Hello,

Thank you for specifying. To better understand the workflow you have, please specify how Microsoft 365 licenses with access to Exchange Online are assigned. Is it done in Adaxes, or a group-based licensing is used?

---

We use group-based licensing. We also experienced this issue with the account that didn't receive a Microsoft 365 license, but instead used its own external mailbox. The email address entered wasn't used because x.500 was already present in the proxy addresses.

Answer 1

Hello,

Thank you for specifying. Since you are using group-based licensing, there is no possibility of modifying SMTP addresses right in the business rule triggering After creating a user. However, it is possible to automate the workflow. To do so, you need to mark the account in the After creating a user business rule for further processing (e.g. by setting a custom Boolean attribute to True). Then you can create a scheduled task that will check if the user is marked and whether an Exchange mailbox exists. If the conditions are met, the task will modify SMTP addresses and clear the mark. Finally, you should have something like the following:

Business rule

Scheduled task