Azure Web Sites, Kudu, List of best hookup sites blogger. There is nothing wrong with this approach, which gives you a high level API experience with intellisense. But I don’t want to use a library!
On the other hand, some developers with knowledge of the API prefer to be close to the wire and call the REST API directly, without using specific libraries. And doing this with the Azure API is actually pretty easy, once you get passed the authentication part. The first step is to obtain an authentication token for your Service Principal. The sample includes a helper function to do this, that you can copy in your code.
All it’s doing is set the Authorization header with the token, and set the base URL so we don’t have to specify it on every request. I have a few more examples in the sample app, so check it out. What if you don’t know the API? Using this, you could have come up with all the samples above without any prior knownledge of the API. JSON like, it’s simple to translate from one to the other. That’s another benefit of the straight REST approach. Since we’re not relying on any libraries, it doesn’t really matter what language you use.
As long as you know how to make http requests, you’re set! Those two things end up working together, but they don’t really know anything about each other. Visual Studio that can make the hookup easier, they don’t cover all scenarios. I will not cover those topics here.
So if you don’t yet have a collection, you’ll need to create one. Or if you already have one, you can add a new job to it. Give some name to your scheduler job. Action type should be https.