Walkthrough Static Web Apps and AAD Authentication

Overview This is a step by step walkthrough of how to add AAD Authentication to Static Web Apps.  This is based on these documents: Quickstart: Building your first static web app with Azure Static Web Apps using the Azure portal | Microsoft Docs Steps Build the Static Web App Using Quickstart: Building your first static

SendGrid 403 authentication Errors

Overview SendGrid – Stopped sending emails due to SendGrid changing authentication requirements for the Sender of the email Background SendGrid changed how they authenticate and require the sender address to be verified. This is not an Microsoft issue.  SendGrid is a 3rd party and solely supported by SendGrid.  You can go to your SendGrid dashboard

Azure App Service–403 causes

Overview There are a few reasons Azure App Services (Azure Web Apps, Azure Function Apps etc…) may get a 403 response.  Other than the code itself returning this, Access Restrictions or IP Restrictions could be at play (and you can mitigate with this knowledge). Causes The site has IP Restrictions in place This will result

Azure Web Job not running

Super simple.  Enable “Always on” for the web site. The SCM Web Site (also known as Kudu) can stop due to inactivity on it or the web site if Always On was not enabled for this site. As discussed at https://docs.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs#scheduling-a-triggered-webjob “A web app can time out after 20 minutes of inactivity. Only requests to

How to chart scale operations for Azure App Services and Function Apps

Overview Application Insights is a powerful tool to visualize what is happening with your application.  This quick query shows how to chart when instances are added and removed Walkthrough Enable application insights for your app using the wizard in the portal or follow our documentation: https://docs.microsoft.com/en-us/azure/azure-monitor/app/azure-web-apps?tabs=net#enable-agent-based-monitoring Open Application Insights from the app of concern from

Azure App Service Authentication CORS error (Easy Auth)

Overview Using Easy Auth you might see this error: Failed to load https://login.windows.net/….: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://sitename.azurewebsites.net‘ is therefore not allowed access. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource

Using Graph Bindings with Node.JS Azure Function Apps

Draft Create a function app and enable AppServices Authentication for AAD but don’t require login.  Use the express settings.  Since we are using the app identity ensure you Allow Anonymous requests. Navigate to the root of the site and Admin Consent access, make sure you can log in. Only if you want to develop local

Easy Auth– Using x-ms-token-aad-access-token as a bearer token

Overview EasyAuth (https://cgillum.tech/category/easy-auth/)  generates an internal access token ‘x-ms-token-aad-access-token‘.  By default this token is an internal only format that you can’t use as a bearer token (it does not even look like one).  You can utilize an unpublished (until now) feature to authenticate against another resource and this will result in a bearer token being