With serverless all the rage at the moment and AWS Lambda’s and Azure Functions offering us easy routes into serverless in the cloud, I thought it about time I actually looked at what I need to do to create a simple Azure function.
Creating a function using the portal
- Log into https://portal.azure.com/
- From the Dashboard select New
- Select Function App
- Supply an App name, set your subscription, location etc. then press Create (I pinned mine the dashboard also using the Pin to dashboard checkbox)
- After a while (it’s not instant) you’ll be met with options for your Function Apps, Functions, Proxies and Slots.
- Click in the + of functions
- Select HttpTrigger – C# or whatever your preferred language is, other triggers can be investigated later but this basically creates a simple REST like function, perfect for quick testing
- Give your function a name and for now leave the Authorization level alone
I used the default name etc and got the following code generated for me by Azure’s wizard.
Note: Whilst there is some information out there on renaming Azure functions, the current portal doesn’t seem to support this, so best to get your name right first time or be prepared to copy and paste code for now into a new function.
using System.Net;
public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
{
log.Info("C# HTTP trigger function processed a request.");
// parse query parameter
string name = req.GetQueryNameValuePairs()
.FirstOrDefault(q => string.Compare(q.Key, "name", true) == 0)
.Value;
// Get request body
dynamic data = await req.Content.ReadAsAsync<object>();
// Set name to query string or body data
name = name ?? data?.name;
return name == null
? req.CreateResponse(HttpStatusCode.BadRequest, "Please pass a name on the query string or in the request body")
: req.CreateResponse(HttpStatusCode.OK, "Hello " + name);
}
This is basically the Hello World of Azure functions. If you run it from the portal you’ll see the output “Hello Azure” as well as logs output. The request box allows you to edit the “name” field which is sent to the function.
By default the authorization level is Function, which basically means that a key is required to run this function. If you click the </> Get function URL link, Azure will supply the fully URL, minus the request payload and this will include the text code=abc123 where abc123 represents a much longer key.
Note: you can find your keys also via the Manage option below the Functions list on the left of the portal. Click the “Click to show” on Function Keys default.
We can remove the requirement for the key and make the function accessible to anonymous users by selecting the Integrate option under the Function name on the left list of the portal and changing Authorization level to Anonymous.
Beware that you’ll be allowing anyone to call your function with the Anonymous option which ultimately ends with your account paying for usage.
Now, once you have the URL for you function just append &name=World to it and navigate to the function via your browser (remove the code= text and don’t bother with the & for anonymous access).
Creating and deploying from Visual Studio 2017
If you have the Azure tools installed then you can create Azure functions directly in Visual Studio (I’m using 2017 for this example).
- File | New Project
- Select Cloud | Azure Functions (or search for it via the search box)
- Name your project, mine’s HelloWorldFunctions
- At this point I build the project to bring in the NuGet packages required – you can obviously do this later
- Add a new item to the project, select Azure Function, mine’s named Echo.cs
- Select HttpTrigger to create a REST like function
- Leave Access rights to Function unless you want Anonymous access
When completed, we again get the default Hello Azure/World sample code. We’re not going to bother changing this at this time, but instead will look to deploy to Azure. But first, let’s test this function in Visual Studio (offline). Simply click the run button and a console window will open with a web server running mimicking Azure, mine creates makes the function available via
http://localhost:7071/api/Echo
If we run this from a web browser and add the ?name=, like this
http://localhost:7071/api/Echo?name=Mark
we’ll get “Hello Mark” returned.
Okay, so it’s working fine, let’s deploy/publish it.
- Right mouse click on the project
- Select Publish…
- Either create new or select existing (if you already have an app), you may need to enter your account details at this point
- In my case I created the application via the Portal first so I selected existing and then select my application from the options available
- Press OK
- Eventually the Publish button will enable, then press this
This will actually publish/deploy the DLL with your Azure function(s) to the Azure application. When you view the function in the Azure Portal you won’t see any source code as you’ve actually just deployed the compiled DLL instead.
In the portal, add your Request body, i.e.
{
"name" : "Azure"
}
and run from the Portal – this is basically a replica (at the functional level) of the portal’s created default function.
Let’s look at the code
I’m going to show the code created via the Visual Studio template here
public static class Echo
{
[FunctionName("Echo")]
public static async Task<HttpResponseMessage> Run(
[HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)]
HttpRequestMessage req, TraceWriter log)
{
log.Info("C# HTTP trigger function processed a request.");
// parse query parameter
string name = req.GetQueryNameValuePairs()
.FirstOrDefault(q => string.Compare(q.Key, "name", true) == 0)
.Value;
// Get request body
dynamic data = await req.Content.ReadAsAsync<object>();
// Set name to query string or body data
name = name ?? data?.name;
return name == null ?
req.CreateResponse(HttpStatusCode.BadRequest,
"Please pass a name on the query string or in the request body")
: req.CreateResponse(HttpStatusCode.OK, "Hello " + name);
}
}
If you’ve used any C# or Java HTTP like functions, this will all seem pretty familiar.
Our function is passed two parameters, the first being the HTTP request message and the second is the logging object. Obviously the logger is pretty self explanatory.
The HttpRequestMessage contains all those sorts of things we’d expect for an HTTP request, i.e. query name parameters, headers, content etc. and like many similar types of functions we return an HTTP response along with a result code.