> 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-resources-and-permissions.md).

# Plan Azure Resources and Permissions

Plan the Azure resources, network configuration, permissions, and quota needed to deploy Silk.

Before deploying Silk on Azure, confirm that your Azure environment has the resources, capacity, and permissions required for your planned configuration. Early planning helps prevent delays when you deploy Flex, create a cluster, and provision DataPods.

Work with your Azure administrator and Silk to confirm your deployment requirements before creating resources or requesting a cluster configuration file.

{% stepper %}
{% step %}

## Complete the pre-installation site survey

Before you create resource groups or subnets, work with the Silk deployment team to complete a pre-installation site survey. The survey captures the information needed to design your deployment, including:

* Target Azure subscription and region
* Deployment and identity management model
* Planned cluster size and DataPod configurations
* Available network address space and subnet CIDR ranges
* Required Azure VM/disk availability and quota

Complete the survey before requesting a cluster configuration file from Silk Support. The cluster file contains configuration details specific to your environment and is required to create a Silk cluster.

{% hint style="warning" %}
If key inputs like subnet CIDR ranges change after Silk generates the file, you'll need to request a new one.
{% endhint %}
{% endstep %}

{% step %}

## Choose a deployment model

Silk supports two deployment models on Azure. Your choice determines how Flex authenticates with Azure, who manages permissions, and which network resources you prepare before deployment.

<table><thead><tr><th width="149.629638671875">Domain</th><th>Flex-managed mode (SMI)</th><th>Customer-managed mode (UMI)</th></tr></thead><tbody><tr><td><strong>Identity</strong></td><td>Uses a system-assigned managed identity (SMI) associated with Flex.</td><td>Uses a user-assigned managed identity (UMI) that your organization creates and manages.</td></tr><tr><td><strong>Permissions</strong></td><td>Flex creates and manages the required roles and role assignments. The deploying user needs Owner permissions on the Flex resource group during installation.</td><td>Your organization assigns the required permissions to the identity and maintains them over time.</td></tr><tr><td><strong>Networking</strong></td><td>You prepare the VNet and Flex subnet. Flex creates the remaining cluster subnets during cluster creation.</td><td>You prepare the VNet, all required subnets, and network security groups (NSGs) before deployment.</td></tr><tr><td><strong>Best suited for</strong></td><td>Environments that allow Flex to manage identities and associated permissions.</td><td>Environments that require customer ownership of identities, permissions, and network configuration.</td></tr></tbody></table>

Both models can use a new or existing Azure VNet. If you need to use pre-created cluster subnets or customer-managed NSGs, choose **customer-managed mode**.

{% hint style="info" %}
**Planning consideration**

Customer-managed keys for Azure Managed Disk (Premium SSD v2) disk encryption are currently supported only with Flex-managed mode. If you plan to use customer-managed keys, include the required Azure Key Vault access in your permissions planning.
{% endhint %}
{% endstep %}

{% step %}

## Plan your Azure resource group and region

### Resource group

Deploy Flex into a **dedicated, empty Azure resource group**. You can create the resource group before deployment or during Azure Marketplace deployment.

The resource group serves as the container for the Silk resources created during deployment and operation. Plan a separate resource group for each environment (e.g., production and non-production) and confirm that the appropriate permissions can be assigned at that scope.

If you use customer-managed mode, plan these additional resource groups, separate from the empty Flex deployment resource group:

* **Identity resource group:** Contains the user-assigned managed identity.
* **Networking resource group:** Contains the VNet, subnets, and NSGs.

### Region and availability zone

Choose an Azure region that supports the resources in your deployment plan, including:

* VM size used by Flex
* VM families used by DataPod nodes, including c.nodes and d.nodes, or m.nodes for Managed Disk deployments
* Required disk types, including Azure Premium SSD v2 if applicable

Depending on your workload and performance requirements, your DataPods may use more than one c.node VM family. Confirm availability for each VM family in your plan.

If you plan to deploy in a specific availability zone, confirm that the required VM sizes are available in that zone. Your Silk deployment team can help identify the resources needed for your configuration.
{% endstep %}

{% step %}

## Plan your network

Silk uses an Azure VNet and dedicated subnets for Flex and cluster communication. Confirm the VNet, available address space, and subnet CIDR ranges for your planned deployment.

When you create the cluster, select a cluster size that determines the address space and the maximum number of Silk resources you can deploy: **Small** (`/24`), **Medium** (`/23`), or **Large** (`/21`). You can't change the cluster size after the cluster is created, so make sure your address space supports the size you need, including future growth.

{% hint style="info" %}
Create the **Flex subnet** before deploying Flex in either deployment model. The Flex subnet must use a `/28` CIDR block and host **only** the Flex VM.

Don't place other workloads in this subnet.
{% endhint %}

The network preparation depends on your deployment model:

* **Flex-managed mode:** After the Flex subnet is created, Flex creates the remaining five cluster subnets during cluster creation.
* **Customer-managed mode:** Your organization creates the six cluster subnets (Flex, External Management, Data 1, Data 2, Internal 1, and Internal 2) and their NSGs before deployment.

When you manage the subnets and NSGs, use the Silk-provided NSG templates and share your configuration with Silk Support for validation before deployment.

### Plan outbound connectivity

Flex needs outbound HTTPS connectivity to Azure services and Silk endpoints during deployment and ongoing operation. Azure no longer provides default outbound internet access for virtual machines in private subnets, so confirm that the Flex subnet has an explicit outbound connectivity method, like an Azure NAT Gateway, Azure Firewall, or another solution that meets your organization's network requirements. Without one, Flex deployment fails.

If your organization restricts outbound traffic, plan the required NSG and firewall rules as well.
{% endstep %}

{% step %}

## Plan permissions

The permissions required to deploy and operate Silk depend on your deployment model. Coordinate with your Azure administrator to ensure that the deploying user and Flex identity have the necessary access.

### Flex-managed mode

The user performing the deployment must have the **Owner** role on the Flex deployment resource group during deployment. Flex creates and manages the required identity, roles, and role assignments at the resource group scope.

To let Flex set up the required VNet roles automatically, the deploying user also needs the **Owner** role on the VNet. If your organization's policies don't allow this, plan for an administrator to create and assign the VNet roles manually.

If you want Flex to create a NAT Gateway during Azure Marketplace deployment, the deploying user also needs permissions to create it. If you use customer-managed keys, Flex also needs access to the associated Azure Key Vault.

### Customer-managed mode

Before deploying Flex, create a user-assigned managed identity and assign the permissions it needs at the applicable scopes:

* **Flex deployment resource group:** Permissions to create and manage the compute, storage, and supporting resources used by Silk. The built-in **Contributor** role is sufficient for most deployments, or you can use an existing custom role that includes the required permissions.
* **Deployment VNet:** Permissions to read the VNet and subnets and to attach resources to the subnets. These permissions don't map to a single built-in role, so plan to create a custom role before assigning it to the identity.

All permissions must be assigned before you start the Azure Marketplace deployment.

The deploying user also needs the permissions required to complete the deployment and assign the identity.
{% endstep %}

{% step %}

## Check resource availability and quota

Azure resource availability and subscription quota are separate considerations. A VM family may be available in your selected region but still require a quota increase before you can deploy the planned resources.

With guidance from Silk, confirm availability and sufficient quota for:

<table><thead><tr><th width="150.74072265625">Domain</th><th>Description</th></tr></thead><tbody><tr><td><strong>Compute</strong></td><td>The Flex VM and the VM families used by your DataPod nodes, including c.nodes, d.nodes, and m.nodes as applicable.</td></tr><tr><td><strong>Storage</strong></td><td>The managed disks required for Flex and DataPod nodes, including Premium SSD v2 disks if applicable. Managed Disk deployments support up to 120 TiB per m.node and up to 360 TiB per DataPod.</td></tr><tr><td><strong>Networking</strong></td><td>Resources like load balancers, public IP addresses (when applicable), and network interfaces.</td></tr></tbody></table>

Account for both your initial configuration and anticipated growth, and review Azure policies or subscription restrictions that could affect resource deployment.

If your quota is insufficient, request an increase before deployment. Some increases can be requested through the Azure portal, while others may require an Azure Support request.
{% endstep %}

{% step %}

## Prepare for Silk image delivery

Silk provides the c.node and d.node images, and Flex copies them into your subscription during cluster creation. The images must be available before you create DataPods.

Confirm that the Flex subnet can reach Azure Storage and Silk services over HTTPS, and that storage network restrictions don't block access from the Flex subnet. Contact [Silk Support](https://support.silk.us) if you need help accessing the images.
{% endstep %}

{% step %}

## Confirm Azure Marketplace access

The Silk deployment package is available through Azure Marketplace. Before launching the deployment, confirm that:

* The deploying user can deploy Azure Marketplace resources, create VMs, and assign managed identities in the target subscription
* The required resource providers (`Microsoft.Compute`, `Microsoft.Network`, and `Microsoft.Storage`) are registered in the subscription

If the deploying user can't deploy Marketplace resources, the Silk installation will fail.
{% endstep %}
{% endstepper %}

For complete deployment requirements and instructions, see the [Silk on Azure Deployment Guide](https://support.silk.us/sys/document/preview/v8610-Silk-on-Azure-Deployment-Guide-260311063805727.pdf).


---

# 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-resources-and-permissions.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.
