Skip to content

Commit d1e3a41

Browse files
committed
Edits2
1 parent fa62162 commit d1e3a41

4 files changed

Lines changed: 4 additions & 5 deletions

File tree

-7.58 KB
Loading
3.68 KB
Loading
-40.1 KB
Loading

articles/azure-functions/openapi-apim-integrate-visual-studio.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The Azure Functions project template in Visual Studio creates a project that you
4040

4141
1. In **Configure your new project**, enter a **Project name** for your project like `TurbineRepair`, and then select **Next**.
4242

43-
1. For the **Create a new Azure Functions application** settings, select one of these options for **Functions worker**, where the option you choose depends on your chosen process model:
43+
1. For the **Additional information** settings, select one of these options for **Functions worker**, where the option you choose depends on your chosen process model:
4444

4545
### [Isolated worker model](#tab/isolated-process)
4646

@@ -60,7 +60,6 @@ The Azure Functions project template in Visual Studio creates a project that you
6060
| ------------ | ------- |----------------------------------------- |
6161
| **Function template** | **Empty** | This creates a project without a trigger, which gives you more control over the name of the HTTP triggered function when you add it later. |
6262
| **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. |
63-
| **Authorization level** | **Function** | When running in Azure, clients must provide a key when accessing the endpoint. For more information, see [Authorization level](functions-bindings-http-webhook-trigger.md#http-auth). |
6463

6564
1. Select **Create** to create the function project.
6665

@@ -153,7 +152,7 @@ Before you can publish your project, you must have a function app in your Azure
153152
154153
1. In **Solution Explorer**, right-click the project and select **Publish** and in **Target**. Select **Azure** and then **Next**.
155154
156-
1. For the **Specific target**, choose **Azure Function App (Windows)** to create a function app that runs on Windows. Then select **Next**.
155+
1. For the **Specific target**, choose **Azure Function App** to create a function app that runs on Windows. Then select **Next**.
157156
158157
1. In **Function Instance**, choose **+ Create a new Azure Function...**.
159158
@@ -166,7 +165,7 @@ Before you can publish your project, you must have a function app in your Azure
166165
| **Name** | Globally unique name | Name that uniquely identifies your new function app. Accept this name or enter a new name. Valid characters are: `a-z`, `0-9`, and `-`. |
167166
| **Subscription** | Your subscription | The Azure subscription to use. Accept this subscription, or select a new one from the drop-down list. |
168167
| **[Resource group](../azure-resource-manager/management/overview.md)** | Name of your resource group | The resource group in which to create your function app. Select an existing resource group from the drop-down list, or choose **New** to create a new resource group.|
169-
| **[Plan Type](functions-scale.md)** | Consumption | When you publish your project to a function app that runs in a [Consumption plan](consumption-plan.md), you pay only for executions of your functions app. Other hosting plans incur higher costs. |
168+
| **[Plan Type](functions-scale.md)** | Flex Consumption | When you publish your project to a function app that runs in a [Flex Consumption plan](consumption-plan.md), you pay only for executions of your functions app. Other hosting plans incur higher costs. |
170169
| **Location** | Location of the service | Choose a **Location** in a [region](https://azure.microsoft.com/regions/) near you or other services your functions access. |
171170
| **[Azure Storage](storage-considerations.md)** | General-purpose storage account | The Functions runtime requires an Azure Storage account. Select **New** to configure a general-purpose storage account. You can also choose an existing account that meets the [storage account requirements](storage-considerations.md#storage-account-requirements). |
172171
@@ -176,7 +175,7 @@ Before you can publish your project, you must have a function app in your Azure
176175
177176
1. Back in **Functions instance**, make sure that **Run from package file** is checked. Your function app is deployed using [Zip Deploy](functions-deployment-technologies.md#zip-deploy) with [Run-From-Package](run-functions-from-deployment-package.md) mode enabled. This deployment method is recommended for your functions project, since it results in better performance.
178177
179-
1. Select **Next**, and in the **API Management** page, also choose **+ Create an API Management API**.
178+
1. Select **Next**, and in the **API Management** page, also choose **+ Create new** or **Create a new instance**.
180179
181180
1. Create an **API in API Management** by using values in the following table:
182181

0 commit comments

Comments
 (0)