Skip to main content

Azure Static Web App - Authentication using pre-configured providers

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.

I ended 2023 with a post about protecting access to your Azure Static Web App using a password. Of course this is a poor man’s implementation of security. So let us have a look today on how to properly integrate authentication in our Azure Static Web App.

Authentication in itself is a broad topic, we can further refine it in 2 parts:

  • Who are you? The real authentication part
  • What are you allowed to do? This is more a question of authorization instead of authentication

Let us focus on the first question in this post. To allow a Static Web App to know who you are we need to integrate with an authentication provider. 

Pre-configuration authentication providers

Azure Static Web Apps comes with 2 pre-configured authentication providers:

  • Github
  • Azure Active Directory (Microsoft Entra ID)

Remark: Originally there was also a pre-configured provider for Twitter(X) but this got removed. 

To authenticate against one of the preconfigured providers you need to browse to a specific endpoint:

Then I embedded this in my navigation component:

Authorization Provider Endpoint
Microsoft Entra ID /.auth/login/aad
Github /.auth/login/github

Both providers are enabled by default. If you want to disable one of them you need to do this by blocking access to this endpoint through the staticwebapps.json.config file:

Next to the built-in providers, it is also possible to configure one or more custom providers but I’ll leave that for a later post.


To authenticate, you need to send the user to one of the above endpoints. Here is an example on how I did this in an Angular application:

I first created a login component that renders a link for a specific authentication provider:

This renders a (simple) UI that looks like this:

When clicking on a specific authentication provider the user is redirected and is requested to authenticate against the selected provider:

After being authenticated we can receive the user information by sending a GET request to the /.auth/me endpoint. This will return a JSON object like the following:

In my Angular app I added some extra logic to call this endpoint and receive the user info:

More information

Authenticate and authorize Static Web Apps | Microsoft Learn

Accessing user information in 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.