> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/deploy/deploy-on-azure/plan-azure-networking-and-connectivity.md).

# Plan Azure Networking and Connectivity

Plan the subnets, security controls, and connectivity required to deploy and operate Silk in Azure.

Before deploying Silk in Azure, plan the network paths required for management, storage access, replication, and communication with Azure and Silk services. Your networking configuration must support installation, ongoing operations, and future upgrades.

Finalize your VNet, subnet address ranges, networking ownership, and outbound connectivity before Marketplace deployment.

{% stepper %}
{% step %}

## Plan your VNet and subnet address space

All six [Silk subnets](#plan-the-required-subnets) must reside in one Azure virtual network (VNet). Silk supports a dedicated VNet or a shared VNet that also contains application or database hosts.

Where possible, place Silk and the hosts that access its storage in the same VNet. This simplifies routing and reduces the configuration required for host connectivity. If hosts reside in another VNet or network segment, plan the routing or VNet peering required for them to reach the Silk data interfaces.

Plan your address space around your intended cluster size: **Small** (`/24`), **Medium** (`/23`), or **Large** (`/21`). Cluster size determines the maximum number of Silk resources you can deploy, and it can't be changed after the cluster is created. Choose a size that supports your expected growth.

### Determine who manages the subnets

Your deployment mode determines which networking resources you create before deployment:

| Networking responsibility                | Flex-managed mode (SMI)                     | Customer-managed mode (UMI)                              |
| ---------------------------------------- | ------------------------------------------- | -------------------------------------------------------- |
| Create the VNet and Flex subnet          | Your organization                           | Your organization                                        |
| Create the five non-Flex cluster subnets | Flex creates them (during cluster creation) | Your organization creates them (before cluster creation) |
| Configure cluster NSGs                   | Flex configures them                        | Your organization creates and maintains them             |
| Provide the required outbound path       | Your organization                           | Your organization                                        |

Using an existing VNet and a pre-created Flex subnet doesn't, by itself, require customer-managed mode.

Use customer-managed mode if your organization needs to pre-create and manage the cluster subnets and their NSGs. In customer-managed mode, place the VNet, subnets, and NSGs in a networking resource group separate from the Flex deployment resource group. Silk provides NSG templates for customer-managed deployments. Share your subnet and NSG configuration with Silk Support for review before deployment.

For identity and permissions requirements, see [Plan Azure Resources and Permissions](/deploy/deploy-on-azure/plan-azure-resources-and-permissions.md).

### Plan the required subnets

Silk separates management, host storage access, replication, and internal communication across six subnets. Size each subnet according to your pre-installation site survey.

<table><thead><tr><th width="144.814697265625">Subnet</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Flex</strong></td><td>Hosts the Flex VM and its management interface. Requires a <code>/28</code> subnet.</td></tr><tr><td><strong>External Management</strong></td><td>Provides DataPod management access, including the SDP Management Console, APIs, and administrative SSH when required.</td></tr><tr><td><strong>Data 1</strong></td><td>Carries iSCSI storage traffic between application or database hosts and DataPods.</td></tr><tr><td><strong>Data 2</strong></td><td>Carries replication traffic between DataPods.</td></tr><tr><td><strong>Internal 1</strong></td><td>Carries internal communication between DataPod components.</td></tr><tr><td><strong>Internal 2</strong></td><td>Carries additional internal communication between DataPod components.</td></tr></tbody></table>

{% hint style="info" %}
**Reserve the Flex subnet for Flex only.**

The Flex subnet hosts only the Flex VM. Don't place other workloads in this subnet.
{% endhint %}
{% endstep %}

{% step %}

## Choose an outbound connectivity method

Flex requires outbound HTTPS connectivity over TCP port 443 to the Azure services and Silk endpoints listed in the next step. These connections support authentication, infrastructure operations, image and artifact downloads, monitoring, and call home.

Provide an explicit outbound path for the Flex subnet before deployment. You can use a NAT Gateway or route traffic through your organization's firewall, egress appliance, or proxy architecture. Service endpoints provide connectivity to selected Azure services, but the remaining required destinations still need an outbound path.

{% hint style="warning" %}
**Azure doesn't provide default outbound access for private subnets.**

Virtual machines in private subnets no longer get default outbound internet access. If the Flex subnet has no explicit outbound path, Flex deployment fails.
{% endhint %}

### Use a NAT Gateway or centralized egress

Supported outbound approaches include:

* Azure NAT Gateway
* Azure Firewall
* Third-party egress appliances
* User-defined routes that direct traffic through an outbound connectivity solution
* A proxy-based architecture

If you use an existing NAT Gateway, confirm that it's deployed in the **same Azure region and availability zone as Flex**, has a **public IP address** assigned, is **attached to the Flex subnet**, and has its **TCP idle timeout set to 120 minutes**.

You can also choose automatic NAT Gateway creation during Azure Marketplace deployment. This option is disabled by default and requires additional deployment permissions.

Ensure that the selected outbound path remains available during both installation and future upgrades.

### Use an HTTPS proxy

If your organization requires a proxy, obtain the proxy address and configuration requirements from your network team before deploying Flex.

Confirm that the proxy:

* Allows outbound HTTPS traffic over TCP port 443
* Permits access to the required Azure and Silk destinations
* Has SSL inspection disabled for Silk traffic
* Provides sufficient availability and bandwidth for image downloads and upgrades

If the proxy requires authentication, confirm the supported authentication method with Silk Support.

Plan Azure Storage and Azure Container Registry service endpoints alongside the proxy configuration so the required Azure service traffic can use those paths.
{% endstep %}

{% step %}

## Allow access to required services

Review NSGs, firewall policies, route tables, proxy policies, and storage account network restrictions together. An outbound route alone doesn't ensure that the required traffic is permitted.

### Plan Azure service endpoints

Configure service endpoints for Azure Storage and Azure Container Registry:

* **Flex-managed mode:** Flex subnet
* **Customer-managed mode:** Flex and External Management subnets

Service endpoints don't replace NSG rules or service-side access policies. Confirm that the network restrictions on the Flex storage account used for image staging permit the access required for image delivery and call home.

### Permit required outbound destinations

Allow outbound HTTPS over TCP port 443 to the applicable destinations below:

<table data-search="false"><thead><tr><th width="248.5184326171875">Destination</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Azure Storage</strong></td><td>Image delivery, artifact access, call home, and lifecycle operations</td></tr><tr><td><strong>Azure Container Registry</strong></td><td>Container image and artifact downloads during installation, cluster creation, and upgrades</td></tr><tr><td><strong>Azure control plane</strong></td><td>Azure resource deployment and ongoing infrastructure operations</td></tr><tr><td><strong><code>login.microsoftonline.com</code></strong></td><td>Azure authentication</td></tr><tr><td><strong><code>*.azure.com</code></strong></td><td>Required Azure service and control-plane communication</td></tr><tr><td><strong><code>*.blob.core.windows.net</code></strong></td><td>Azure Blob Storage access identified in the Flex call home requirements</td></tr><tr><td><strong><code>hub.clarity.silk.us</code></strong><br><strong><code>(34.120.213.129)</code></strong></td><td>Communication with Silk Clarity for monitoring, telemetry, and platform lifecycle operations</td></tr></tbody></table>

Use the appropriate Azure service tags where applicable and domain or IP rules where required by your firewall architecture. Ensure that allow rules take precedence over outbound deny rules.

For the complete NSG, service tag, and firewall requirements, see the [Silk on Azure Deployment Guide](https://support.silk.us/sys/document/preview/v8610-Silk-on-Azure-Deployment-Guide-260311063805727.pdf) (requires Silk Support Portal access).
{% endstep %}

{% step %}

## Plan administrative access

Flex doesn't require inbound internet access. Administrators typically connect through a VPN, bastion host, or jump host that can reach the Flex management interface.

Identify the administrator networks and systems that need access, then configure routing and security rules for those sources.

Plan access to:

* **Flex** for cluster and DataPod management
* **External Management interfaces** for SDP Management Console and API access, as well as administrative SSH when required

Use HTTPS (TCP port 443) for browser-based management. Restrict this access according to your organization's security policies. In customer-managed mode, include any additional administrative or support access in the NSG configuration you share with Silk Support.
{% endstep %}

{% step %}

## Plan host and replication connectivity

Plan the following communication paths, keeping host storage traffic and replication traffic on their designated subnets:

<table><thead><tr><th width="268.5185546875">Communication path</th><th>Planning requirement</th></tr></thead><tbody><tr><td><strong>Application or database hosts</strong> <i class="fa-arrow-right">:arrow-right:</i> <strong>Data 1 interfaces</strong></td><td><p>Provide routing and security rules for iSCSI storage access.</p><p></p><p>Flex configures <code>dataport01</code> on each c.node for iSCSI traffic during deployment and scale-out.</p></td></tr><tr><td><strong>Replication peers</strong> <i class="fa-arrows-left-right">:arrows-left-right:</i> <strong>Data 2 interfaces</strong></td><td><p>Provide connectivity in both directions between the participating DataPods.</p><p></p><p>Flex configures <code>dataport02</code> on each c.node for replication during deployment and scale-out. Allow inbound and outbound replication traffic on TCP ports 55855-55858.</p></td></tr><tr><td><strong>Management systems or replication peers</strong> <i class="fa-arrows-left-right">:arrows-left-right:</i> <strong>External Management interfaces</strong></td><td>Permit the required management communication, including HTTPS over TCP port 443.</td></tr><tr><td><strong>DataPod components</strong> <i class="fa-arrows-left-right">:arrows-left-right:</i> <strong>Internal 1 and Internal 2</strong></td><td>Preserve the internal communication allowed by the Silk NSG configuration.</td></tr></tbody></table>

If hosts or replication peers reside outside the Silk VNet, confirm that routing, peering, and firewall policies support the required paths in both directions.

If the replication subnets of the source and target DataPods don't match, also plan static routes between them. You configure static routes on each DataPod in the SDP Management Console.

Host configuration, iSCSI sessions, and multipathing require additional preparation beyond Azure network access.
{% endstep %}

{% step %}

## Confirm network readiness

Before deploying Flex, confirm that:

* [ ] The dedicated Flex `/28` subnet exists.
* [ ] Customer-managed cluster subnets and NSGs are ready and have been reviewed by Silk Support, if applicable.
* [ ] The Flex subnet has an explicit outbound path.
* [ ] Required Azure services and Silk endpoints are reachable over HTTPS.
* [ ] Service endpoints and storage account network policies permit the required access.
* [ ] Administrators can reach the management interfaces through the planned access path.
* [ ] Host and replication networks have the required routes and security rules.

Keep the finalized subnet design, cluster size, and deployment mode consistent with the information provided to Silk Support for your cluster file. If key inputs change after the file is generated, request a new cluster file.
{% endstep %}
{% endstepper %}


---

# 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.silk.us/deploy/deploy-on-azure/plan-azure-networking-and-connectivity.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.
