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/application-gateway/application-gateway-private-deployment.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Each of these features can be configured independently. For example, a public IP
37
37
38
38
The functionality of the new controls of private IP frontend configuration, control over NSG rules, and control over route tables, are generally available and supported in production. To join enable the feature, you must opt in to the experience using the Azure portal, PowerShell, CLI, or REST API.
39
39
40
-
When enrolled, all new Application Gateways provision with the ability to define any combination of the NSG, Route Table, or private IP configuration features. If you wish to opt out from the new functionality and return to the current generally available functionality of Application Gateway, you can do so by [unregistering from the feature](#unregister-the-feature).
40
+
When enrolled, all new Application Gateways provision with the ability to define any combination of the NSG, Route Table, or private IP configuration features. If you wish to opt out from the new functionality, you can do so by [unregistering from the feature](#unregister-the-feature).
You can view preview functionality on the [Azure Functions SQL Extensions release page](https://github.com/Azure/azure-functions-sql-extension/releases).
116
-
117
-
> [!NOTE]
118
-
> Breaking changes between preview releases of the Azure SQL bindings for Azure Functions requires that all Functions targeting the same database use the same version of the SQL extension package.
119
-
120
-
---
121
-
122
-
::: zone-end
123
-
124
-
125
-
::: zone pivot="programming-language-python"
126
-
127
-
## Functions runtime
128
-
129
-
<!-- > [!NOTE]
130
-
> Python language support for the SQL bindings extension is available starting with v4.5.0 of the [functions runtime](./set-runtime-version.md#view-and-update-the-current-runtime-version). You might need to update your install of Azure Functions [Core Tools](functions-run-local.md) for local development. -->
131
-
132
-
133
-
## Install bundle
134
-
135
-
The SQL bindings extension is part of the v4 [extension bundle], which is specified in your host.json project file.
136
-
137
-
138
-
# [Bundle v4.x](#tab/extensionv4)
139
-
140
-
The extension bundle is specified by the following code in your `host.json` file:
You can view preview functionality on the [Azure Functions SQL Extensions release page](https://github.com/Azure/azure-functions-sql-extension/releases).
167
-
168
-
> [!NOTE]
169
-
> Breaking changes between preview releases of the Azure SQL bindings for Azure Functions requires that all Functions targeting the same database use the same version of the SQL extension package.
170
-
171
-
---
172
-
173
-
::: zone-end
174
-
175
-
176
-
::: zone pivot="programming-language-java"
177
-
178
-
179
-
## Install bundle
180
-
181
-
The SQL bindings extension is part of the v4 [extension bundle], which is specified in your host.json project file.
182
-
183
-
# [Bundle v4.x](#tab/extensionv4)
184
-
185
-
The extension bundle is specified by the following code in your `host.json` file:
If your app needs to use preview functionality, you should instead reference the latest version of the preview bundle. For more information, see [Preview extension bundles](extension-bundles.md#preview-extension-bundles).
210
83
211
84
You can view preview functionality on the [Azure Functions SQL Extensions release page](https://github.com/Azure/azure-functions-sql-extension/releases).
212
85
213
86
> [!NOTE]
214
87
> Breaking changes between preview releases of the Azure SQL bindings for Azure Functions requires that all Functions targeting the same database use the same version of the SQL extension package.
215
88
216
-
---
217
-
89
+
::: zone-end
90
+
::: zone pivot="programming-language-java"
218
91
## Update packages
219
92
220
-
Add the Java library for SQL bindings to your functions project with an update to the `pom.xml` file in your Java Azure Functions project as seen in the following snippet:
93
+
Add the [Azure Functions Java SQL Types package](https://mvnrepository.com/artifact/com.microsoft.azure.functions/azure-functions-java-library-sql)to your functions project with an update to the `pom.xml` file in your project, as in this example:
221
94
222
95
```xml
223
96
<dependency>
@@ -227,16 +100,6 @@ Add the Java library for SQL bindings to your functions project with an update t
227
100
</dependency>
228
101
```
229
102
230
-
You can use the preview extension bundle with an update to the `pom.xml` file in your Java Azure Functions project as seen in the following snippet:
Add the [Azure Functions Java Redis Annotations package](https://mvnrepository.com/artifact/com.microsoft.azure.functions/azure-functions-java-library-redis) to your project by updating the `pom.xml` file to add this dependency:
Azure Redis triggers and bindings have a required property that indicates the application setting or collection name that contains cache connection information. The Redis trigger or binding looks for an environmental variable holding the connection string with the name passed to the `Connection` parameter.
105
92
106
-
::: zone-end
107
-
::: zone pivot="programming-language-javascript,programming-language-python,programming-language-powershell"
93
+
In local development, the `Connection` can be defined using the [local.settings.json](/azure/azure-functions/functions-develop-local#local-settings-file) file. When deployed to Azure, [application settings](/azure/azure-functions/functions-how-to-use-azure-function-app-settings) can be used.
108
94
109
-
Add the extension bundle by adding or replacing the following code in your _host.json_ file:
95
+
When connecting to a cache instance with an Azure function, you can use one of these kinds of connections in your deployments:
A user-assigned mananged identity must be associated with your function app, and that identity must also be granted explicit permissions in your cache service. For more information, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
121
100
122
-
>[!WARNING]
123
-
>The Redis extension is currently only available in a preview bundle release.
The built-in system-assigned mananged identity must be enabled in your function app, and that identity must also be granted explicit permissions in your cache service. For more information, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
127
104
128
-
##Redis connectionstring
105
+
### [Connection string](#tab/connection-string)
129
106
130
-
Azure Redis triggers and bindings have a required property that indicates the application setting or collection name that contains cache connection information. The connection string can be found on the [**Access keys**](/azure/azure-cache-for-redis/cache-configure#access-keys) menu in the Azure Managed Redis or Azure Cache for Redis portal. The Redis trigger or binding looks for an environmental variable holding the connection string with the name passed to the `Connection` parameter.
107
+
The connection string can be found on the [**Access keys**](/azure/azure-cache-for-redis/cache-configure#access-keys) menu in the Azure Managed Redis or Azure Cache for Redis portal.
131
108
132
-
In local development, the `Connection` can be defined using the [local.settings.json](/azure/azure-functions/functions-develop-local#local-settings-file) file. When deployed to Azure, [application settings](/azure/azure-functions/functions-how-to-use-azure-function-app-settings) can be used.
109
+
For optimal security, your function app should use Microsoft Entra ID with managed identities to authorize requests against your cache, if possible. Authorization by using Microsoft Entra ID and managed identities provides superior security and ease of use over shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
133
110
134
-
When connecting to a cache instance with an Azure function, you can use three types of connections in your deployments: Connection string, System-assigned managed identity, and User-assigned managed identity.
111
+
### [Service principal](#tab/service-principal)
135
112
136
-
For local development, you can also use service principal secrets.
113
+
Connecting to the service using a service principal is only supported when running locally during development. A service principal linked to your account must be granted explicit permissions in your cache service.
Use the `appsettings`to configure each of the following types of client authentication, assuming the `Connection`was set to `Redis` in the function.
117
+
These examples show the key name and value of app settings required to connect to each cache service based on the kind of client authentication, assuming that the `Connection`property in the binding is set to `Redis`.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments