> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/inforiver-enterprise-on-prem/deployment/microsoft-azure/networking.md).

# Networking

In this section, you will configure the networking for the Inforiver deployment.

* You can either use an existing virtual network (bring your own VNet) or create a new virtual network from this section.
* If you are using an existing virtual network, ensure that the required subnets have been created according to the deployment requirements. Select the existing virtual network from the drop-down list, and then choose the appropriate **Private**, **Public**, and **Background** subnets. 
* If you choose to create a new virtual network, you can retain the default configuration and proceed to the next section.
* If you want to modify the default virtual network configuration, select **Edit virtual network**. In the pane that opens, update the address space and subnet configurations as required. Ensure that the **Private**, **Public** and **Background** subnets each have at least 32 IP addresses (/27) allocated. If the background processor is deployed on AKS, allocate at least 256 IP addresses (/24) for the Background subnet.
* Configure the AKS Service CIDR, which defines the cluster-internal Kubernetes service address range. The Service CIDR must not overlap with the virtual network (VNet) address space. 
* Specify the AKS DNS Service IP. This IP address must belong to the configured AKS Service CIDR.
* Optional: To deploy a NAT gateway with a standard public IP attached to all subnets, select the **Deploy NAT Gateway** checkbox. This feature is not available for *Bring Your Own VNet*.
* Optional: To deploy the AKS cluster as a private cluster, select **Make AKS Cluster Private**.

You may also change the **VNet** and **subnet names** while you are in the edit network screen. The VNet name provided here would be concatenated with the solution name and used while creating the virtual network.

<figure><img src="https://4102771481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftn9fmavAcyzaE7MAMP2U%2Fuploads%2FnniEV9wupAFnzb2EViOs%2Fimage.png?alt=media&amp;token=041c6e1a-8e41-4314-8cf5-73848407a1ec" alt=""><figcaption><p>Networking details</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inforiver.com/inforiver-enterprise-on-prem/deployment/microsoft-azure/networking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.