> 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/azure-deployment-overview.md).

# Azure Deployment Overview

Understand how Silk fits into your Azure environment, choose a deployment model, and explore the main stages of deployment.

Silk runs within your Azure environment, providing storage for your database and application workloads. A deployment includes Silk Flex for orchestration and management along with Silk DataPods that provide storage to connected hosts.

You deploy Flex from the Azure Marketplace into a dedicated Flex resource group, then use Flex to create a cluster, provision DataPods, and connect your database hosts. Before installation, choose a deployment model and prepare the Azure networking, permissions, and resource capacity required for your planned environment.

## Azure deployment architecture

A Silk deployment includes Silk Flex, one or more DataPods, and the network connections that support management, storage access, and internal communication. Azure resources and services provide the underlying compute, storage, networking, and identity capabilities.

The following architecture diagram shows how Flex, DataPods, and application hosts fit within an Azure environment, along with Silk Clarity.

<figure><img src="https://3771785211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRoeFiUtkaS7g8f3vjz5%2Fuploads%2FsVBUGKCbXds1jfRBfDll%2Fazure-architecture.png?alt=media" alt="Silk on Azure deployment architecture"><figcaption><p>Silk on Azure deployment architecture</p></figcaption></figure>

Application hosts access storage provided by DataPods over iSCSI. Flex manages the deployment and lifecycle of Silk resources, while network connections support host access, communication between Silk components, and access to required external services.

## Key deployment components

<table data-search="false"><thead><tr><th width="243.7037353515625">Component</th><th>Deployment role</th></tr></thead><tbody><tr><td><strong>Azure VNets and subnets</strong></td><td>Silk runs within an Azure virtual network (VNet), using dedicated subnets for Flex, DataPod management, storage access, replication, and internal communication.</td></tr><tr><td><strong>Flex resource group</strong></td><td>A dedicated, empty resource group in your Azure subscription that will contain Flex, the Silk cluster, and your DataPods.<br><br>Silk resources stay in your subscription, separate from the resource groups that hold your VNet and application hosts.</td></tr><tr><td><strong>Silk Flex</strong></td><td>Orchestrates deployment and ongoing management of your Silk environment. You install Flex from the Azure Marketplace, then use it to create a cluster, deploy DataPods, and manage their lifecycle.<br><br>Flex uses an Azure managed identity with the permissions required for your selected deployment model.</td></tr><tr><td><strong>Silk DataPods</strong></td><td>Provide storage and data services for your workloads. They run on Azure compute and storage resources and are deployed and managed through Flex.<br><br>DataPod compute nodes (c.nodes) process storage I/O, while data nodes (d.nodes) provide the underlying storage resources. d.nodes are grouped into protected media nodes (m.nodes), and the compute and storage layers scale independently.<br><br>A Silk cluster provides the shared deployment context and network topology for one or more DataPods.</td></tr><tr><td><strong>Application hosts</strong></td><td>Your applications and databases run on hosts that access storage presented by the DataPods. These hosts require connectivity to the Silk storage network and configuration that follows Silk host connectivity best practices.</td></tr><tr><td><strong>Azure deployment and infrastructure services</strong></td><td>The Azure Marketplace provides the installation path for Flex. Azure virtual machines, disks, network interfaces, and related resources provide the infrastructure used by Flex and DataPods.</td></tr><tr><td><strong>Supporting Azure and Silk services</strong></td><td>Silk Clarity provides monitoring, telemetry, and call home over outbound HTTPS. No inbound access from Silk is required.<br><br>Flex also uses Azure services such as Microsoft Entra ID (authentication), Azure Resource Manager, Azure Storage (image and artifact delivery), and Azure Container Registry. These connections require the outbound access and network security configuration described in the deployment documentation.</td></tr></tbody></table>

## Network connections

Silk uses six dedicated subnets within one VNet:

* **Flex:** Hosts the Flex VM management instance.
* **External Management:** Supports administrative access and management communication.
* **Data 1:** Carries storage traffic between application hosts and DataPods.
* **Data 2:** Carries replication traffic between DataPods.
* **Internal 1 and Internal 2:** Support communication between DataPod components.

Silk supports a dedicated VNet or a shared VNet that also contains application or database host subnets. The Flex subnet is always customer-created, while responsibility for the remaining subnets depends on your deployment model.

Flex also requires outbound HTTPS connectivity to the Azure services and Silk endpoints used for authentication, image and artifact downloads, telemetry, and lifecycle operations. Configure the required network security rules and outbound access before installation.

Plan sufficient VNet address space for your intended cluster configuration, connectivity from application hosts, and access to required Azure and Silk services.

## Deployment workflow

{% stepper %}
{% step %}

### Plan the deployment

Work with the Silk deployment team to complete a pre-installation site survey. Confirm the target subscription, region, cluster size, networking, resource availability, and quota requirements.

Choose one of two deployment models below. Both deployment models support deployment into a new or existing VNet. Choose the model that best fits your organization's networking and identity governance requirements:

<table><thead><tr><th width="287.7777099609375">Deployment model</th><th>Management responsibilities</th></tr></thead><tbody><tr><td><strong>Flex-managed mode (SMI)</strong></td><td>Uses a system-assigned managed identity (SMI).<br><br>You prepare the VNet and Flex subnet. Flex creates the remaining cluster subnets and manages the required identities and permissions as described in the deployment documentation.</td></tr><tr><td><strong>Customer-managed mode (UMI)</strong></td><td>Uses a user-assigned managed identity (UMI).<br><br>You prepare and manage all required subnets, network security groups, and identity permissions. Flex uses these resources to deploy and manage Silk.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Prepare the Azure environment

Prepare the resource group, VNet, subnets, network security rules, and managed identity permissions required by your deployment model.

Validate resource availability and quota, establish outbound connectivity for Flex, and obtain an environment-specific cluster file from Silk Support. Finalize deployment inputs before requesting the file because configuration changes may require a replacement file.
{% endstep %}

{% step %}

### Deploy Flex

Deploy Flex from the Azure Marketplace into the prepared resource group and Flex subnet.

During deployment, select the Azure location, VM configuration, networking, and identity settings appropriate for your organization.
{% endstep %}

{% step %}

### Create the Silk cluster

Open Flex and use the cluster file to create your Silk cluster:

* For Flex-managed deployments, Flex creates the remaining cluster subnets.
* For customer-managed deployments, select the subnets your organization prepared.

The cluster size determines the deployment's supported scale and cannot be changed after cluster creation. Choose a size that accommodates your expected growth.

Verify that the required Silk images are available before proceeding with DataPod creation.
{% endstep %}

{% step %}

### Provision storage and connect hosts

Use Flex to create DataPods for your planned workloads. Then provision volumes, configure host access, and connect your database hosts using the applicable Silk host connectivity guidance.

You can also complete additional management configuration, like single sign-on through Microsoft Entra ID.
{% endstep %}
{% endstepper %}

## Next steps

For guidance on configuration planning, see [Plan a Silk Deployment](/deploy/plan-your-deployment/plan-a-silk-deployment.md) and [Cluster and DataPod Sizing](/deploy/plan-your-deployment/cluster-and-datapod-sizing.md).


---

# 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/azure-deployment-overview.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.
