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/flex-consumption-plan.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
@@ -141,7 +141,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
141
141
+**Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#managed-dependencies-feature) aren't supported by Flex Consumption. You must instead [upload modules with app content](functions-reference-powershell.md#including-modules-in-app-content).
142
142
+**Diagnostic settings**: Diagnostic settings aren't currently supported.
143
143
+**Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting, managed certificates, app service certificates, and other platform certificate-based features are currently not supported.
144
-
+**Key Vault References**: Key Vaultreferencesin app settings don't work when Key Vault is network access restricted, even if the function app has Virtual Network integration. The current workaround is to directly reference the Key Vault in code and read the required secrets.
144
+
+**Key Vault and App Configuration References**: You can't currently use [Azure Key Vault](../app-service/app-service-key-vault-references.md) or [Azure App Configuration](../app-service/app-service-configuration-references.md) references in your Flex Consumption plan app settings when these services are network access restricted. This limitation applies even when the function app has Virtual Network integration enabled. If you must use restricted Key Vault or App Configuration instances, you must use client SDKs to manually retrieve values from references in these services. Functions binding extensions also can't access these references, which means you must also use Azure client SDKs for accessing remote service data from your function code.
145
145
+**Timezones**: `WEBSITE_TIME_ZONE` and `TZ` app settings are not currently supported when running on Flex Consumption plan.
# Azure Database for MySQL bindings for Azure Functions overview (Preview)
18
+
# Overview of Azure Database for MySQL bindings for Azure Functions (preview)
19
19
20
-
This set of articles explains how to work with [Azure Database for MySQL](/azure/mysql/index) bindings in Azure Functions. For preview, Azure Functions supports input bindings and output bindings for Azure Database for MySQL.
20
+
This set of articles explains how to work with [Azure Database for MySQL](/azure/mysql/index) bindings in Azure Functions. For the preview, Azure Functions supports input bindings and output bindings for Azure Database for MySQL.
21
21
22
22
| Action | Type |
23
23
|---------|---------|
24
24
| Read data from a database |[Input binding](./functions-bindings-azure-mysql-input.md)|
25
25
| Save data to a database |[Output binding](./functions-bindings-azure-mysql-output.md)|
26
-
| Trigger a function when a change is detected on a MySQL Table|[Trigger binding](./functions-bindings-azure-mysql-trigger.md)|
26
+
| Trigger a function when a change is detected in a MySQL table|[Trigger binding](./functions-bindings-azure-mysql-trigger.md)|
27
27
28
28
::: zone pivot="programming-language-csharp"
29
29
30
-
## Install extension
30
+
## Install the extension
31
31
32
-
The extension NuGet package you install depends on the C# mode you're using in your function app:
32
+
The extension NuGet package that you install depends on the C# mode you're using in your function app:
33
33
34
34
# [Isolated worker model](#tab/isolated-process)
35
35
36
-
Functions execute in an isolated C# worker process. To learn more, see [Guide for running C# Azure Functions in an isolated worker process](dotnet-isolated-process-guide.md).
36
+
Functions run in an isolated C# worker process. To learn more, see [Guide for running C# Azure functions in an isolated worker process](dotnet-isolated-process-guide.md).
37
37
38
-
Add the extension to your project by installing this [NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.MySql/1.0.3-preview/).
38
+
Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.MySql/1.0.3-preview/).
Functions execute in the same process as the Functions host. To learn more, see [Develop C# class library functions using Azure Functions](functions-dotnet-class-library.md).
46
+
Functions run in the same process as the Azure Functions host. To learn more, see [Develop C# class library functions using Azure Functions](functions-dotnet-class-library.md).
47
47
48
-
Add the extension to your project by installing this [NuGet package](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.MySql/1.0.3-preview).
48
+
Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.MySql/1.0.3-preview).
::: zone pivot="programming-language-javascript, programming-language-powershell"
60
59
61
-
## Install bundle
60
+
## Install the bundle
62
61
63
-
The MySQL bindings extension is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles), which is specified in your host.json project file.
62
+
The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles). This bundle is specified in your host.json project file.
64
63
65
-
### Preview Bundle v4.x
64
+
### Preview bundle v4.x
66
65
67
-
You can use the preview extension bundle by adding or replacing the following code in your `host.json` file:
66
+
You can use the preview extension bundle by adding or replacing the following code in your host.json file:
68
67
69
68
```json
70
69
{
@@ -80,20 +79,15 @@ You can use the preview extension bundle by adding or replacing the following co
80
79
81
80
::: zone-end
82
81
83
-
84
82
::: zone pivot="programming-language-python"
85
83
86
-
## Functions runtime
87
-
88
-
89
-
## Install bundle
84
+
## Install the bundle
90
85
91
-
The MySQL bindings extension is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles), which is specified in your host.json project file.
86
+
The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles). This bundle is specified in your host.json project file.
92
87
88
+
### Preview bundle v4.x
93
89
94
-
### Preview Bundle v4.x
95
-
96
-
You can use the preview extension bundle by adding or replacing the following code in your `host.json` file:
90
+
You can use the preview extension bundle by adding or replacing the following code in your host.json file:
97
91
98
92
```json
99
93
{
@@ -109,17 +103,15 @@ You can use the preview extension bundle by adding or replacing the following co
109
103
110
104
::: zone-end
111
105
112
-
113
106
::: zone pivot="programming-language-java"
114
107
108
+
## Install the bundle
115
109
116
-
## Install bundle
110
+
The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles). This bundle is specified in your host.json project file.
117
111
118
-
The MySQL bindings extension is part of the v4 [extension bundle](./functions-bindings-register.md#extension-bundles), which is specified in your host.json project file.
112
+
### Preview bundle v4.x
119
113
120
-
### Preview Bundle v4.x
121
-
122
-
You can use the preview extension bundle by adding or replacing the following code in your `host.json` file:
114
+
You can use the preview extension bundle by adding or replacing the following code in your host.json file:
123
115
124
116
```json
125
117
{
@@ -135,7 +127,7 @@ You can use the preview extension bundle by adding or replacing the following co
135
127
136
128
## Update packages
137
129
138
-
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:
130
+
You can use the preview extension bundle with an update to the pom.xml file in your Java Azure Functions project, as shown in the following snippet:
139
131
140
132
```xml
141
133
<dependency>
@@ -149,27 +141,26 @@ You can use the preview extension bundle with an update to the `pom.xml` file in
149
141
150
142
## MySQL connection string
151
143
152
-
Azure Database for MySQL bindings for Azure Functions have a required property for the connection string on all bindings. These pass the connection string to the MySql.Data.MySqlClient library and supports the connection string as defined in the [MySqlClient ConnectionString documentation](https://dev.mysql.com/doc/connector-net/en/connector-net-connections-string.html). Notable keywords include:
144
+
Azure Database for MySQL bindings for Azure Functions have a required property for the connection string. These bindings pass the connection string to the MySql.Data.MySqlClient library and provide support as defined in the [MySqlClient ConnectionString documentation](https://dev.mysql.com/doc/connector-net/en/connector-net-connections-string.html). Notable keywords include:
153
145
154
-
-`server` the host on which the server instance is running. The value can be a host name, IPv4 address, or IPv6 address.
155
-
-`uid` the MySQL user account to provide for the authentication process
156
-
-`pwd` the password to use for the authentication process.
157
-
-`database` The default database for the connection. If no database is specified, the connection has no default database
146
+
-`server`: The host on which the server instance is running. The value can be a host name, IPv4 address, or IPv6 address.
147
+
-`uid`: The MySQL user account to provide for the authentication process.
148
+
-`pwd`: The password to use for the authentication process.
149
+
-`database`: The default database for the connection. If no database is specified, the connection has no default database.
158
150
159
151
## Considerations
160
152
161
-
- Azure Database for MySQL binding supports version 4.x and later of the Functions runtime.
162
-
-Source code for the Azure Database for MySQL bindings can be found in [this GitHub repository](https://github.com/Azure/azure-functions-mysql-extension/tree/main/src).
163
-
-This binding requires connectivity to an Azure Database for MySQL.
164
-
- Output bindings against tables with columns of spatial data types `GEOMETRY`, `POINT`, or`POLYGON` aren't supported and data upserts will fail.
153
+
- Azure Database for MySQL bindings support version 4.x and later of the Azure Functions runtime.
154
+
-You can find source code for the Azure Database for MySQL bindings in [this GitHub repository](https://github.com/Azure/azure-functions-mysql-extension/tree/main/src).
155
+
-These bindings require connectivity to Azure Database for MySQL.
156
+
- Output bindings against tables with columns of spatial data types `GEOMETRY`, `POINT`, and`POLYGON` aren't supported. Data upserts fail.
165
157
166
158
## Samples
167
159
168
-
In addition to the samples for C#, Java, JavaScript, PowerShell, and Python available in the [Azure MySQL bindings GitHub repository](https://github.com/Azure/azure-functions-mysql-extension/tree/main/samples), more are available in Azure Samples.
169
-
160
+
In addition to the samples for C#, Java, JavaScript, PowerShell, and Python available in the [GitHub repository for Azure Database for MySQL bindings](https://github.com/Azure/azure-functions-mysql-extension/tree/main/samples), more are available in [Azure Samples](https://github.com/Azure-Samples).
170
161
171
-
## Next steps
162
+
## Related content
172
163
173
-
-[Read data from a database (Input binding)](./functions-bindings-azure-mysql-input.md)
174
-
-[Save data to a database (Output binding)](./functions-bindings-azure-mysql-output.md)
175
-
-[Trigger a function when a change is detected on a table (Trigger binding)](./functions-bindings-azure-mysql-trigger.md)
164
+
-[Read data from a database (input binding)](./functions-bindings-azure-mysql-input.md)
165
+
-[Save data to a database (output binding)](./functions-bindings-azure-mysql-output.md)
166
+
-[Trigger a function when a change is detected in a table (trigger binding)](./functions-bindings-azure-mysql-trigger.md)
Copy file name to clipboardExpand all lines: articles/azure-vmware/azure-vmware-solution-known-issues.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
@@ -36,7 +36,7 @@ Refer to the table to find details about resolution dates or possible workaround
36
36
| When I run the VMware HCX Service Mesh Diagnostic wizard, all diagnostic tests will be passed (green check mark), yet failed probes will be reported. See [HCX - Service Mesh diagnostics test returns 2 failed probes](https://knowledge.broadcom.com/external/article?legacyId=96708)| 2024 | Fixed in 4.9+. | Resolved in [HCX 4.9.2](https://docs.vmware.com/en/VMware-HCX/4.9.2/rn/vmware-hcx-492-release-notes/index.html#What's%20New)|
37
37
| The AV64 SKU currently supports RAID-1 FTT1, RAID-5 FTT1, and RAID-1 FTT2 vSAN storage policies. For more information, see [AV64 supported RAID configuration](introduction.md#av64-supported-raid-configuration)| Nov 2023 | The AV64 SKU now supports 7 Fault Domains and all vSAN storage policies. For more information, see [AV64 supported Azure regions](architecture-private-clouds.md#azure-region-availability-zone-to-host-type-mapping-table)| June 2024 |
38
38
| [VMSA-2023-023](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/23677) VMware vCenter Server Out-of-Bounds Write Vulnerability (CVE-2023-34048) publicized in October 2023 | October 2023 | A risk assessment of CVE-2023-03048 was conducted and it was determined that sufficient controls are in place within Azure VMware Solution to reduce the risk of CVE-2023-03048 from a CVSS Base Score of 9.8 to an adjusted Environmental Score of [6.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/MAC:L/MPR:H/MUI:R) or lower. Adjustments from the base score were possible due to the network isolation of the Azure VMware Solution vCenter Server (ports 2012, 2014, and 2020 aren't exposed via any interactive network path) and multiple levels of authentication and authorization necessary to gain interactive access to the vCenter Server network segment. Azure VMware Solution is currently rolling out [7.0U3o](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3o-release-notes.html) to address this issue. | March 2024 - Resolved in [ESXi 7.0U3o](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-70u3o-release-notes.html) |
39
-
| After my private cloud NSX-T Data Center upgrade to version [3.2.2](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/3-2/release-notes/vmware-nsxt-data-center-322-release-notes.html), the NSX-T Manager **DNS - Forwarder Upstream Server Timeout** alarm is raised | February 2023 |[Enable private cloud internet Access](architecture-design-public-internet-access.md), alarm is raised because NSX-T Manager can't access the configured CloudFlare DNS server. Otherwise, [change the default DNS zone to point to a valid and reachable DNS server.](configure-dns-azure-vmware-solution.md)| February 2023 |
39
+
| After my private cloud NSX-T Data Center upgrade to version [3.2.2](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/3-2/release-notes/vmware-nsxt-data-center-322-release-notes.html), the NSX-T Manager **DNS - Forwarder Upstream Server Timeout** alarm is raised | February 2023 |[Enable private cloud internet Access](architecture-design-public-internet-access.md), alarm is raised because NSX-T Manager can't access the configured Cloudflare DNS server. Otherwise, [change the default DNS zone to point to a valid and reachable DNS server.](configure-dns-azure-vmware-solution.md)| February 2023 |
40
40
| After my private cloud NSX-T Data Center upgrade to version [3.2.2](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/3-2/release-notes/vmware-nsxt-data-center-322-release-notes.html), the NSX-T Manager **Capacity - Maximum Capacity Threshold** alarm is raised | 2023 | Alarm raised because there are more than four clusters in the private cloud with the medium form factor for the NSX-T Data Center Unified Appliance. The form factor needs to be scaled up to large. This issue should get detected through Microsoft, however you can also open a support request. | 2023 |
41
41
| When I build a VMware HCX Service Mesh with the Enterprise license, the Replication Assisted vMotion Migration option isn't available. | 2023 | The default VMware HCX Compute Profile doesn't have the Replication Assisted vMotion Migration option enabled. From the Azure VMware Solution vSphere Client, select the VMware HCX option and edit the default Compute Profile to enable Replication Assisted vMotion Migration. | 2023 |
42
42
| When first logging in to the vSphere Client, the **Cluster-n: vSAN health alarms are suppressed** alert is active in the vSphere Client | 2021 | The alert should be considered an informational message, since Microsoft manages the service. Select the **Reset to Green** link to clear it. | 2021 |
Copy file name to clipboardExpand all lines: articles/azure-vmware/deploy-disaster-recovery-using-jetstream.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,10 @@ For full details, refer to the article: [Disaster Recovery with Azure NetApp Fil
108
108
-[Azure Blob Storage account](../storage/common/storage-account-create.md) created using either Standard or Premium Performance tier. For [access tier, select **Hot**](../storage/blobs/access-tiers-overview.md).
109
109
110
110
>[!NOTE]
111
-
>The **Enable hierarchical namespace** option on the blob isn't supported.
111
+
>The **Enable hierarchical namespace** option on the blob isn't supported.
112
+
113
+
>[!NOTE]
114
+
>Protecting a **shared disk** (eg WFC) is not supported.
112
115
113
116
- An NSX-T network segment configured on Azure VMware Solution private cloud with DHCP enabled on the segment for the transient JetStream Virtual appliances is employed during recovery or failover.
0 commit comments