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
<sup>1</sup> Deployment technology that requires [manual trigger syncing](#trigger-syncing). Deployment Center no longer shows the FTP/FTPS Credentials. If these are still needed then you can download the publishing profile.
<sup>1</sup> Deployment technologies that require you to [manually sync triggers](#trigger-syncing) aren't recommended.
50
50
<sup>2</sup> In-portal editing is disabled when code is deployed to your function app from outside the portal. For more information, including language support details for in-portal editing, see [Language support details](supported-languages.md#language-support-details).
51
51
<sup>3</sup> In-portal editing is enabled only for HTTP and Timer triggered functions running on Linux in Premium and Dedicated plans.
52
52
@@ -186,11 +186,11 @@ Use cloud sync to sync your content from Dropbox and OneDrive to Azure Functions
186
186
187
187
>__Where app content is stored:__ The app content is in the cloud store, but a local copy is stored on the app file system, which may be backed by Azure Files from the storage account specified when the function app was created.
188
188
189
-
### FTP
189
+
### FTPS
190
190
191
-
You can use FTP to directly transfer files to Azure Functions.
191
+
You can use FTPS to directly transfer files to Azure Functions, athough this deployment method isn't recommended.
192
192
193
-
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md&tabs=cli). Note that FTP/S deployment isn't available in the Azure portal, but you can use [Azure CLI](../app-service/deploy-ftp.md&tabs=cli) or [Azure PowerShell](../app-service/deploy-ftp.md&tabs=powershell).
193
+
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md?tabs=cli). Note that FTP/S deployment isn't available in the Azure portal, but you can use [Azure CLI](../app-service/deploy-ftp.md?tabs=cli) or [Azure PowerShell](../app-service/deploy-ftp.md&tabs=powershell).
194
194
195
195
>__When to use it:__ To reduce the chance of errors, you should avoid using deployment methods that require the additional step of [manually syncing triggers](#trigger-syncing). Use [zip deployment](run-functions-from-deployment-package.md) when possible.
When you develop a function app locally, you must maintain local copies of these values in the local.settings.json project file. To learn more, see [Local settings file](functions-develop-local.md#local-settings-file).
86
86
87
+
## FTPS deployment settings
88
+
89
+
Azure Functions supports deploying code to your function app by using FTPS. Because this deployment method requires you to [sync triggers](functions-deployment-technologies.md#trigger-syncing), it's not recommended. T securely transfer project files, always use FTPS and not FTP.
90
+
91
+
You can get the credentials required for FTPS deployment using one of these methods:
92
+
93
+
### [Portal](#tab/portal)
94
+
95
+
You can get the FTPS publishing credentials in the Azure portal by downloading the publishing profile for your function app.
96
+
97
+
> [!IMPORTANT]
98
+
> The publishing profile contains important security credentials. You should always secure the downloaded file on your local computer.
3. In the file, locate the `publishProfile` element with the attribute `publishMethod="FTP"`. In this element, the `publishUrl`, `userName`, and `userPWD` attributes contain the target URL and credentials for FTPS publishing.
103
+
104
+
### [Azure CLI](#tab/azure-cli)
105
+
106
+
Run this Azure CLI command that returns the FTPS credentials from the publishing profile.
In this example, replace `<APP_NAME>` with your function app name and `<GROUP_NAME>` with the resource group. The returned `URL`, `username`, and `password` columns contain the target URL and credentials for FTPS publishing.
113
+
114
+
### [Azure PowerShell](#tab/azure-powershell)
115
+
116
+
---
117
+
87
118
## Hosting plan type
88
119
89
120
When you create a function app, you also create a hosting plan in which the app runs. A plan can have one or more function apps. The functionality, scaling, and pricing of your functions depend on the type of plan. To learn more, see [Azure Functions hosting options](functions-scale.md).
@@ -98,13 +129,13 @@ The following values indicate the plan type:
|[Dedicated (App Service)](dedicated-plan.md)| Various | Various |
100
131
101
-
# [Portal](#tab/portal)
132
+
###[Portal](#tab/portal)
102
133
103
134
To determine the type of plan used by your function app, see **App Service plan** in the **Overview** tab for the function app in the [Azure portal](https://portal.azure.com). To see the pricing tier, select the name of the **App Service Plan**, and then select **Properties** from the left pane.
104
135
105
136

106
137
107
-
# [Azure CLI](#tab/azure-cli)
138
+
###[Azure CLI](#tab/azure-cli)
108
139
109
140
Run the following Azure CLI command to get your hosting plan type:
0 commit comments