Hi Alfredo,
Everything has bugs - including Azure - and they always cause problems at the most inopportune moment possible.
Anyway, as it turns out, I really don't need JIT at all. Whatever it was doing to cause this problem in a previously stable environment, I don't know.
So, my time-tested tactic is to walk around walls instead of bashing my head them.
I just fixed the issue directly in network - and I now realize that I don't really need JIT. I will just manage that stuff manually so that I know what is going on, and I can also scale back the service level to exclude JIT - and save quite a bit of money (on my minimal budget).
Don't know where these messages get propagated to - but maybe this will be a useful pointer to someone else.
Regards,
Derek