This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(76.8, 98%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Hello I've inherited a network where they have mailboxes in exchange online (cloud) and also have on-prem exchange 2016 server still running . (no mailboxes left on-prem. )
MX records are Exchange online. I'm not sure why the on-prem server is still running . Is there any best practices I can do in order to determine whether or not it's still actually required for anything? Do i need to analyze the hybrid connector somehow? Should I just power it off? What is the best practice in this scenario.
I am writing here to confirm with you any update about this thread now?
If the suggestion below helps, please be free to mark it as an answer for helping more people.
No, that wont happen. Removing Exchange doesnt remove the mail attributes of user objects.
thanks @Andy David - MVP I was hoping you would chime in LOL
So..... the Microsoft Documentation is Inaccurate or ????
Which documentation says that ? :)
it mentions it here in this article . as per @Vasil Michev 's first post.
https://learn.microsoft.com/en-us/exchange/decommission-on-premises-exchange
Right, thats the management piece, its not supported to remove the last Exchange server when using AADConnect, but the objects themselves still retain their mail attributes
so things like modifying the ProxyAddress atrrib are no longer possible from the on-prem server / adsiedit , adding additional smtp / alias needs to be done from office 365, is this what we are saying ?
if so that 's totally acceptable from most orgs i would think .
Oh no, you can still modify the on-prem attributes using ADUC or ADSIEDIT and they will sync using AADConnect.
Its just technically not supported, but you can certainly still do it or use 3rd party products to do so.
It all depends where the authoring of the attributes is. If AADConnect is still used, then the support level requires at least one Exch Server to manage those attributes, but that doesnt mean you cant remove Exchange and manage them directly with ADUC or ADSIEDIT.