Deploy OpenAPI enabled Azure Functions with .NET in Visual Studio | Azure Friday

Justin Yoo joins Scott Hanselman to demonstrate an extension he developed for adding OpenAPI capabilities to Azure Functions apps. See how easy it is to get HTTP-triggered .NET functions with OpenAPI support and deploy an Azure Functions app with Azure API Management from Visual Studio.

0:00 – Intro
3:15 – Create
9:20 – Publish
12:56 – Consume
22:48 – Wrap-up

Create serverless APIs in Visual Studio using Azure Functions and API Management integration (preview)

Azure Functions OpenAPI Extension

Create a free account (Azure)

#Microsoft #Azure #AzureFriday

[age]

Thanks Justin. Very glad that your package which helped me a lot in my current project now is official Microsoft package!

[panja]

Wov awesome features, thanks for the great video. Thanks Justin and Scott, it really helped me in learning all these features so quick.

[dannythomas]

Would it be possible to have a video that digs deeper into the OpenApi attributes used within Azure Functions, also some guidance on applying attributes to models?

[bikashpattanayak]

I loved this feature. I didn't knew it was there in the first place.

[johnscott]

This is great.. how can we get the OpenAPI to produce the Swagger file and add it to our source code. In our scenario we are using authentication for the functionApp which is blocking access to the swagger url when we are automating our import of the APIM APIs.

[shanksatutube]

HI Justin, do we use Function-App or OpenApi option in APIM to add the API/Az-function. The issue is if i use openAPI and add api using the Swagger.json file, i can see the service contracts, request header etc. But if i use the function-app option, i don't see any data-annotations that are added to the function app, like Parameter, Response etc....

[morrolan]

Only thing is, does anyone deploy like this without vnet, subnet, private endpoint, and oauth ? This may be fine for some quick setup during dev.