You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/openapi-apim-integrate-visual-studio.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,10 @@
2
2
title: Create serverless APIs in Visual Studio using Azure Functions and API Management
3
3
description: Use Visual Studio to create an HTTP triggered function along with an OpenAPI definition, which enables Azure API Management integration so that other apps and services can call your serverless function-based API.
4
4
ms.topic: tutorial
5
-
ms.date: 05/07/2021
5
+
ms.date: 01/18/2023
6
6
---
7
7
8
-
# Create serverless APIs in Visual Studio using Azure Functions and API Management integration (preview)
8
+
# Create serverless APIs in Visual Studio using Azure Functions and API Management integration
9
9
10
10
REST APIs are often described using an OpenAPI definition. This file contains information about operations in an API and how the request and response data for the API should be structured.
11
11
@@ -21,7 +21,7 @@ In this tutorial, you learn how to:
21
21
The serverless function you create provides an API that lets you determine whether an emergency repair on a wind turbine is cost-effective. Because both the function app and API Management instance you create use consumption plans, your cost for completing this tutorial is minimal.
22
22
23
23
> [!NOTE]
24
-
> The OpenAPI and API Management integration featured in this article is currently in preview. This method for exposing a serverless API is only supported for [in-process](functions-dotnet-class-library.md) C# class library functions. [isolated worker process](dotnet-isolated-process-guide.md) C# class library functions and all other language runtimes should instead [use Azure API Management integration from the portal](functions-openapi-definition.md).
24
+
> The OpenAPI and API Management integration featured in this article is currently only supported for [in-process](functions-dotnet-class-library.md) C# class library functions. [Isolated worker process](dotnet-isolated-process-guide.md) C# class library functions and all other language runtimes should instead [use Azure API Management integration from the portal](functions-openapi-definition.md).
25
25
26
26
## Prerequisites
27
27
@@ -43,7 +43,7 @@ The Azure Functions project template in Visual Studio creates a project that you
|**Functions worker**|**.NET 6**| This value creates a function project that runs in-process on version 4.x of the Azure Functions runtime. OpenAPI file generation is only supported for versions 3.x and 4.x of the Functions runtime, and isolated worker process isn't supported. |
46
+
|**Functions worker**|**.NET 6**| This value creates a function project that runs in-process on version 4.x of the Azure Functions runtime, which is required for OpenAPI file generation. |
47
47
|**Function template**|**HTTP trigger with OpenAPI**| This value creates a function triggered by an HTTP request, with the ability to generate an OpenAPI definition file. |
48
48
|**Use Azurite for runtime storage account (AzureWebJobsStorage)**|**Selected**| You can use the emulator for local development of HTTP trigger functions. Because a function app in Azure requires a storage account, one is assigned or created when you publish your project to Azure. |
49
49
|**Authorization level**|**Function**| When running in Azure, clients must provide a key when accessing the endpoint. For more information about keys and authorization, see [function access keys](functions-bindings-http-webhook-trigger.md#authorization-keys). |
0 commit comments