Book Image

Azure Serverless Computing Cookbook - Third Edition

By : Praveen Kumar Sreeram
Book Image

Azure Serverless Computing Cookbook - Third Edition

By: Praveen Kumar Sreeram

Overview of this book

This third edition of Azure Serverless Computing Cookbook guides you through the development of a basic back-end web API that performs simple operations, helping you understand how to persist data in Azure Storage services. You'll cover the integration of Azure Functions with other cloud services, such as notifications (SendGrid and Twilio), Cognitive Services (computer vision), and Logic Apps, to build simple workflow-based applications. With the help of this book, you'll be able to leverage Visual Studio tools to develop, build, test, and deploy Azure functions quickly. It also covers a variety of tools and methods for testing the functionality of Azure functions locally in the developer's workstation and in the cloud environment. Once you're familiar with the core features, you'll explore advanced concepts such as durable functions, starting with a "hello world" example, and learn about the scalable bulk upload use case, which uses durable function patterns, function chaining, and fan-out/fan-in. By the end of this Azure book, you'll have gained the knowledge and practical experience needed to be able to create and deploy Azure applications on serverless architectures efficiently.
Table of Contents (14 chapters)
13
Index

Securing Azure Functions using Azure Active Directory

One of the most important Azure Services related to security is Azure Active Directory (Azure AD). Azure AD is a cloud-based identity and access management service that helps developers to authenticate end users before accessing Azure Functions HTTP triggers. Azure Functions provides an easy way to integrate Azure AD with HTTP triggers called EasyAuth.

Thanks to Azure App Service, from which the EasyAuth feature is inherited, we can integrate Azure function HTTP triggers with Azure AD without writing a single line of code.

Getting ready

In this recipe, to make things simple, let's use the default Active Directory that is created when we create an Azure account. In real-time production scenarios, however, we'd ideally have an existing Active Directory that needs to be integrated. I would recommend going over this article for more information: docs.microsoft.com/azure/active-directory-b2c/tutorial-web-app-dotnet...