Change of SOA of mail users, groups and contacts - does Adaxes understand this?

Question

Hi! I'm wanting to perform the retirement of the last Exchange server in an installation, but I need to adjust the SOA (Start of Authority) of mailboxed users, as well as a bunch of distribution groups and contacts.

Does Adaxes understand the "onPremisesSyncBehavior/isCloudManaged" change on the onprem objects?

Answer 1

Hello,

I'm wanting to perform the retirement of the last Exchange server in an installation, but I need to adjust the SOA (Start of Authority) of mailboxed users, as well as a bunch of distribution groups and contacts.

With Adaxes, there is no need to change the SOA after retiring your last on-premises Exchange server. Everything can keep working just fine. For more details about Adaxes functioning after the procedure and recommended actions, have a look at the following article: https://www.adaxes.com/questions/16903/does-adaxes-function-after-decommissioning-exchange-server.

Does Adaxes understand the "onPremisesSyncBehavior/isCloudManaged" change on the onprem objects?

The attribute does not influence Adaxes functionality. If you are still going to change the SOA, you will also need to make sure that only the corresponding objects are actually updated by your workflows. However, updating the attribute might influence your Adaxes licensing. With the current settings, if you register a Microsoft Entra domain and a synchronized Active Directory domain in Adaxes, synchronized users will only be counted once toward the license limit. With the update you mentioned, it will be two separate accounts consuming two Adaxes licenses.

Comments

OK, maybe i should re-phrase it a bit differently - I have a number of contacts and groups that i want to change the SOA on before I start the Exchange server decom process. I converted a few samples and tested, and when adjusting the object directly in 365 and Exchange Online, it works, but when trying to do this in Adaxes, it adjusts the "old" onprem object even though with SOA changes, anything onprem will no longer be synced up. Should I either set up a Cloud Sync configuration to try and re-sync that info back up, or consider performing a manual migration of those groups and contacts?

---

Hello,

If you set the isCloudManaged attribute to True, the synchronization is no longer in place. The behavior comes from Microsoft and that is the way it works. It is not related to Adaxes. As a result, setting the attribute gives you two separate accounts. For the on-premises AD object in Adaxes you can manage AD properties and on-premises Exchange settings. For the cloud account you can manage their properties and Exchange Online settings. There is no such thing as re-sync or anything like that.