# Optional configurations: Microsoft Azure

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fazure%2Foptional-configurations-microsoft-azure.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fazure%2Foptional-configurations-microsoft-azure.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

A Coralogix function app reaches your storage account or Event Hub over the network. When those resources are closed to public access, the function app needs to sit inside a virtual network (VNet) that can reach them.

## What you need [​](#what-you-need- "Direct link to what-you-need-")

* A function app deployed with **Function App Service Plan Type** set to **Premium**. The Networking feature (and therefore VNet integration) is not available on other plans.
* A virtual network with access to the storage account or Event Hub you want to monitor.

Warning

VNet integration is unavailable on consumption (serverless) plans, which are usually much cheaper. The Premium plan bills for resources continuously rather than per use, so this configuration can cost significantly more.

## Connect the function app to a VNet [​](#connect-the-function-app-to-a-vnet- "Direct link to connect-the-function-app-to-a-vnet-")

1

<!-- -->

.

Open VNet integration

In the function app, select **Networking** in the left-hand panel, then open the **VNet integration** configuration.

2

<!-- -->

.

Add the VNet

Select **Add VNet**, then choose the subscription, virtual network, and subnet that can reach your storage account or Event Hub. Select **OK**.

[![Azure VNet Integration page with the Add VNet control and a panel selecting subscription, virtual network, and subnet](/docs/assets/images/2-2-1024x795-8809a78fff368be88c3703a38b9cef6e.webp)](https://coralogix.com/docs/assets/images/2-2-1024x795-8809a78fff368be88c3703a38b9cef6e.webp)

Shows the function app being attached to a virtual network.

3

<!-- -->

.

Allow the VNet on the resource

On the storage account or Event Hub, select **Networking**, then confirm the virtual network appears under **Virtual networks** with its endpoint enabled.

[![Azure storage account Networking page with public access limited to selected virtual networks and one VNet listed as enabled](/docs/assets/images/3-2-1024x884-a98def5942bc6d5105a73aee187bd125.webp)](https://coralogix.com/docs/assets/images/3-2-1024x884-a98def5942bc6d5105a73aee187bd125.webp)

Shows the resource side of the pairing, where the permitted networks are declared.

Note

If no virtual network is aligned with the resource, select **Add new virtual network**.

Reusing an existing virtual network is a common cause of silent failure: it may be internet-restricted, which blocks the function app's outbound messages to the Coralogix API. When in doubt, create a new VNet dedicated to the Coralogix integration and the private resource.

## Related resources[​](#related-resources "Direct link to Related resources")

[Introduction to Microsoft Azure](https://coralogix.com/docs/integrations/azure/introduction-to-microsoft-azure.md)[Azure Event Hub ARM deployment](https://coralogix.com/docs/integrations/azure/event-hub-microsoft-azure-resource-manager.md)[Azure resource logs](https://coralogix.com/docs/integrations/azure/azure-resource-logs.md)