Oh for sure you want to use TLS, what's insane is the developer experience of needing to implement it yourself.

The author chose a library that didn't support TLS, written by a company that isn't Microsoft. Terrible devex indeed but hard to see why that's the fault of the platform that required TLS.

> There's not enough information to come to a conclusion as to what the 503s originated from.

It's the MS way. I remember writing some code for MS graph and wondering why the hell it isn't working, I'm doing near same thing that doc example did. Nonsense generic error message. Left for the day, ran code next morning, everything works fine.

No message saying "hey the thing behind it is down", just error that was generic enough that it could be my inputs being wrong.

The author did not make any statements that would lead to the conclusion the issue is lack of information provided by the platform, simply they do not state any troubleshooting steps taken.

I've seen these mysterious and unexplained 503s occur

Solution:

1. Delete Function App

2. Deploy again

3. Profit?