Skip to main content

Azure Static Web App - Bring your own API

As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.

In the last post in this series, I explained that with every Static Web App you get a serverless API endpoint (based on Azure Functions) for free. However you have also the option to bring your own API. This can be an Azure Function but also an API exposed through Azure API Management, an Azure App Service or Azure Container Apps.

The advantage of using this feature is that you get:

In this post I’ll show you how to do this and I’ll use Azure Container Apps to demonstrate it.

The Azure Container App

I already created the Azure Container App(ACA) in Visual Studio and deployed it to Azure. Most important is that the ACA exposes an API listening on the /api endpoint.

As I mentioned I deployed the ACA. I didn’t add any authentication or authorization so right now anyone can call this api.

Linking our API

Next step is to link the API to our Azure Static Web App. Therefore we go to our Static Web App in the Azure Portal and click on the APIs section:

To link an API we need to click on the Link hyperlink next to the environment.

Remark: The link option will only be available when Azure Static Web App has detected that no existing Managed Function is found inside your source repository.

On the Link new Backend screen, we can select a Resource Type and select the Resource itself. Click on Link to complete the process.

You can see that the 'withoutapi' environment is now linked to our Azure Container App:

Now our ACA API is no longer directly accessible but can only be called through our Azure Static Web App. 

If you go to the ACA resource in the Azure Portal, you can see that an Azure Static Web App is used as the Identity Provider.

Calling the API

To call our API we first need to make sure that a corresponding route is configured in our staticwebapp.config.json file:

Once that is done, we can invoke the API through our frontend code:

More information

Overview of API support in Azure Static Web Apps | Microsoft Learn

Bring your own functions to Azure Static Web Apps | Microsoft Learn


Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.