Hi David,
Well, you stated it works when running from your Dev machine so, not a problem using Aurelius with Azure SQL.
This error is usually reported for one of 2 reasons: trying to insert on varchar(max) fields with older ODBC driver versions that do not support it or while using newer ODBC versions, do not correcly set the size property (length) of varchar fields.
I guess the Aurelius MS Sql Native Driver is tested against some ODBC versions. You may find usefull to check this other thread with a similar problem (issues with ODBC):
Sorry I don't have a more straightforward solution. TMS support you certainly point you in the right direction.
Regards,