Chiming in on this as well. Just ran into this roadblock. Four years later and it's very disappointing that I have to either break my local config file or go out of my way and script things out (which isn't convenient and not easy to maintain for non-scripters).

Being limited to HTTP/HTTPS bindings is very disappointing, especially given how easy I imagine it should be to implement this (as you can see, others have done so in a few lines of PowerShell).

Not having this is going to severely limit Octopus' usefulness for us. This suggestion is almost four years old and the latest version doesn't have this ability. I assume then you have no intention of supporting this?

This is must have functionality which I would have thought would be relatively easy to include and help so many people!

Script shared by a user to workaround this using Powershell: http://help.octopusdeploy.com/discussions/questions/10067#comment_41423820

It would be incredibly useful to have this funtionality as we have a growing number of WCF services being deployed through Octopus

For those stumbling across this request, there's a PowerShell script here: https://www.codingcurve.com/snippet/481/creating-iis-net-tcp-binding-using-powershell/

@Jesse: mind to share the powershell you use?

I would have a big use for adding this binding native. Currently, I am using PowerShell to fully setup the required protocols.