Gain insights into building, deploying, and managing .NET-based Azure Functions. Learn about function triggers, configuration, scaling, orchestration, and security, while leveraging cost-effective, serverless architecture.

Building and Deploying Azure Functions on NET..png

azurefunctions.tar.gz

Basic Function Job

Function with a HTTP client

Basic Function Job with HTTPS

Azure Functions allows businesses and individual developers to run workloads of varying intensity in the cloud without the need to manage servers. These serverless applications can automatically scale based on demand, ensuring that resources are always available when needed. Azure Functions is also very cost-effective since it bills you only for the functions you use.

In this course, you’ll focus on the .NET implementations of Azure Functions. You’ll start by learning how to build, configure, and deploy these functions. Next, you’ll explore running Azure Functions in a development environment and examine the different types of functions and the various ways to trigger them. Finally, you’ll learn how to orchestrate, scale, and secure Azure Functions.

By the end of this course, you will have gained a comprehensive understanding of the full development cycle of .NET-based Azure functions. You will be equipped to build, deploy, and manage Azure functions in a .NET environment.

Building and Deploying Azure Functions in .NET

Nothing, because it is enabled by default.

Obtain an SSL certificate signed by a recognized certification authority.

What needs to be done to enable HTTPS in Azure Functions?

What needs to be done to enable HTTPS in Azure Functions?

To safelist the domains that are allowed to access the application.

To blocklist the domains so they cannot access the application.

To ensure that only the domains that use HTTPS can access the application.

To ensure that only specific apps can access the resource.

It helps automatically redirect from HTTP to HTTPS.

It makes the function more compliance-friendly.

It ensures that only authorized clients can access Azure Functions.

**(Select all that apply.)** What is the benefit of using HSTS in Azure Functions?

(Select all that apply.) What is the benefit of using HSTS in Azure Functions?

It can only be accessed by a user with the role of `Admin`.

It can only be accessed if the client provides the admin key.

It can only be accessed by a client that is explicitly registered as an admin.

This authorization level only applies to the management API of the function app.

What is the `Admin` authorization level in a function?

What is the <code>Admin</code> authorization level in a function?

The function can only be accessed by another function from the same function App.

The function can only be accessed by another function app as a client.

The function can be accessed only by clients that have the function-level key.

It means that the function cannot use the HTTP trigger.

What is the `Function` authorization level in a function?

What is the <code>Function</code> authorization level in a function?

Test your knowledge on securing Azure Functions.

Introduction

Azure Functions Basics

Azure Functions Triggers and Bindings

Using Durable Functions For Long-Running Operations

Azure Functions Reliability and Availability

Scaling Azure Functions

Securing Azure Functions

Conclusion

Appendix

Quiz: Securing Azure Functions