<div>
Thank you both for your input. This has cemented my decision to no longer use and Edge server. Much appreciated.
</div>


Thank you both for your input. This has cemented my decision to no longer use and Edge server. Much appreciated.

<div>
<div class="content wysiwyg-content">
Good day all,<br />
<br />
Just looking for some opinions here. I have always used Edge Transport servers in my Exchange environments since they became available in 2007. However, I have just completed my organizations migration from 2010 to 2013 and I am considering retiring our old Edge servers and just going straight to our CAS/HUB/Mail servers with inbound SMTP. It seems that is what is most commonly done currently. So anyhow, what &nbsp;say you fellow Exchange admins / engineers? Use Edge Transports again or not? All comments, thoughts and opinions will be greatly appreciated.
</div>
</div>


Good day all,

Just looking for some opinions here. I have always used Edge Transport servers in my Exchange environments since they became available in 2007. However, I have just completed my organizations migration from 2010 to 2013 and I am considering retiring our old Edge servers and just going straight to our CAS/HUB/Mail servers with inbound SMTP. It seems that is what is most commonly done currently. So anyhow, what  say you fellow Exchange admins / engineers? Use Edge Transports again or not? All comments, thoughts and opinions will be greatly appreciated.

Edge Transport Servers in Exchange 2013 - 2016 environment Yes / No?

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.