---
title: Private connectivity with Azure Private Link
description: You can use Azure Private Link to establish a secure connection for your Elastic Cloud deployments to communicate with other Azure services. Azure routes...
url: https://www.elastic.co/docs/deploy-manage/security/private-connectivity-azure
products:
  - Elastic Cloud Hosted
applies_to:
  - Elastic Cloud Hosted: Generally available
---

# Private connectivity with Azure Private Link
You can use Azure Private Link to establish a secure connection for your Elastic Cloud deployments to communicate with other Azure services. Azure routes the Private Link traffic within the Azure data center and never exposes it to the public internet.
Azure Private Link establishes a secure connection between two Azure VNets. The VNets can belong to separate accounts, for example a service provider and their service consumers. Azure routes the Private Link traffic within the Azure data centers and never exposes it to the public internet. In such a configuration, Elastic Cloud is the third-party service provider and the customers are service consumers.
Private Link is a connection between an Azure Private Endpoint and a Azure Private Link Service.
Azure Private Link requires that you also filter traffic to your deployments by creating virtual private connection (VPC) filters as part of your private connection policy in Elastic Cloud. This limits traffic to your deployment to the VPC specified in the policy, as well as any other filters defined in policies applied to the deployment.
To learn how private connection policies impact your deployment, refer to [Network security policies in Elastic Cloud](https://www.elastic.co/docs/deploy-manage/security/network-security-policies).
<tip>
  Elastic Cloud Hosted also supports [IP filters](https://www.elastic.co/docs/deploy-manage/security/ip-filtering-cloud). You can apply both IP filters and private connections to a single Elastic Cloud resource.
</tip>


## Considerations

Private connectivity with Azure Private Link is supported only in Azure regions.

## Limitations

When using Azure Private Link, the following limitations apply:
- **Transport client:** The Elasticsearch transport client is not supported over private connections.
- **Managed OTLP endpoint:** In Elastic Cloud Hosted deployments, the [managed OTLP endpoint](https://www.elastic.co/docs/reference/opentelemetry/motlp) is not accessible over private connections. The public endpoint is still available.
- **SSO to Kibana from the Elastic Cloud console:** You can't use SSO to log in to Kibana endpoints that are protected by private connections. The connection to Kibana public URL is still available.
  As a workaround, you can [add an IP filter](https://www.elastic.co/docs/deploy-manage/security/ip-filtering-cloud) for the hosts that will use SSO through the Elastic Cloud console.
  In Elastic Cloud Hosted, you can still SSO into private Kibana endpoints individually using the [SAML](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/saml) or [OIDC](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect) protocol from your own identity provider, just not through the Elastic Cloud console. Stack-level authentication using the Elasticsearch username and password also works with `{{kibana-id}}.vpce.{region}.aws.elastic-cloud.com` URLs.


## Azure Private Link Service aliases

Private Link Services are set up by Elastic in all supported Azure regions under the following aliases:
<dropdown title="Azure public regions">
  | Region           | Azure Private Link Service alias                                                                                             | Private hosted zone domain name                      |
  |------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|
  | australiaeast    | australiaeast-prod-012-privatelink-service.a0cf0c1a-33ab-4528-81e7-9cb23608f94e.australiaeast.azure.privatelinkservice       | privatelink.australiaeast.azure.elastic-cloud.com    |
  | centralus        | centralus-prod-009-privatelink-service.49a041f7-2ad1-4bd2-9898-fba7f7a1ff77.centralus.azure.privatelinkservice               | privatelink.centralus.azure.elastic-cloud.com        |
  | eastus2          | eastus2-prod-002-privatelink-service.64359fdd-7893-4215-9929-ece3287e1371.eastus2.azure.privatelinkservice                   | privatelink.eastus2.azure.elastic-cloud.com          |
  | francecentral    | francecentral-prod-008-privatelink-service.8ab667fd-e8af-44b2-a347-bd48d109afec.francecentral.azure.privatelinkservice       | privatelink.francecentral.azure.elastic-cloud.com    |
  | japaneast        | japaneast-prod-006-privatelink-service.cfcf2172-917a-4260-b002-3e7183e56fd0.japaneast.azure.privatelinkservice               | privatelink.japaneast.azure.elastic-cloud.com        |
  | northeurope      | northeurope-prod-005-privatelink-service.163e4238-bdde-4a0b-a812-04650bfa41c4.northeurope.azure.privatelinkservice           | privatelink.northeurope.azure.elastic-cloud.com      |
  | southeastasia    | southeastasia-prod-004-privatelink-service.20d67dc0-2a36-40a0-af8d-0e1f997a419d.southeastasia.azure.privatelinkservice       | privatelink.southeastasia.azure.elastic-cloud.com    |
  | uksouth          | uksouth-prod-007-privatelink-service.98758729-06f7-438d-baaa-0cb63e737cdf.uksouth.azure.privatelinkservice                   | privatelink.uksouth.azure.elastic-cloud.com          |
  | westeurope       | westeurope-prod-001-privatelink-service.190cd496-6d79-4ee2-8f23-0667fd5a8ec1.westeurope.azure.privatelinkservice             | privatelink.westeurope.azure.elastic-cloud.com       |
  | westus2          | westus2-prod-003-privatelink-service.b9c176b8-4fe9-41f9-916c-67cacd753ca1.westus2.azure.privatelinkservice                   | privatelink.westus2.azure.elastic-cloud.com          |
  | eastus           | eastus-prod-010-privatelink-service.b5765cd8-1fc8-45e9-91fc-a9b208369f9a.eastus.azure.privatelinkservice                     | privatelink.eastus.azure.elastic-cloud.com           |
  | southcentralus   | southcentralus-prod-013-privatelink-service.f8030986-5fb9-4b0e-8463-69604233b07e.southcentralus.azure.privatelinkservice     | privatelink.southcentralus.azure.elastic-cloud.com   |
  | canadacentral    | canadacentral-prod-011-privatelink-service.203896f1-da53-4c40-b7db-0ba4e17a1019.canadacentral.azure.privatelinkservice       | privatelink.canadacentral.azure.elastic-cloud.com    |
  | brazilsouth      | brazilsouth-prod-014-privatelink-service.05813ca4-cd0f-4692-ad69-a339d023f666.brazilsouth.azure.privatelinkservice           | privatelink.brazilsouth.azure.elastic-cloud.com      |
  | centralindia     | centralindia-prod-016-privatelink-service.071806ca-8101-425b-ae86-737935a719d3.centralindia.azure.privatelinkservice         | privatelink.centralindia.azure.elastic-cloud.com     |
  | southafricanorth | southafricanorth-prod-015-privatelink-service.b443098d-6382-42aa-9025-e0cd3ec9c103.southafricanorth.azure.privatelinkservice | privatelink.southafricanorth.azure.elastic-cloud.com |
</dropdown>


## Set up a private connection

The process of setting up the private connection with Azure Private link is split between Azure (e.g. by using Azure portal), and the Elastic Cloud UI. These are the high-level steps:

| Azure portal                                                                                  | Elastic Cloud                                                                                                   |
|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
| 1. [Create a private endpoint using Elastic Cloud service alias](#ec-private-link-azure-dns). |                                                                                                                 |
| 2. [Create a DNS record pointing to the private endpoint](#ec-private-link-azure-dns).        |                                                                                                                 |
|                                                                                               | 3. [Create a private connection policy](#ec-azure-allow-traffic-from-link-id).                                  |
|                                                                                               | 4. [Associate the Azure private connection policy with your deployments](#associate-private-connection-policy). |
|                                                                                               | 5. **Optional**: [Add an IP filter to allow SSO to Kibana from the Elastic Cloud console.](#sso-kib-ip-filter)  |
|                                                                                               | 6. [Interact with your deployments over Private Link](#ec-azure-access-the-deployment-over-private-link).       |

After you create your private connection policy, you can [edit](#edit-private-connection-policy), [disassociate](#remove-private-connection-policy), or [delete](#delete-private-connection-policy) it.

### Create your private endpoint and DNS entries in Azure

1. Create a private endpoint in your VNet using the alias for your region.
   Follow the [Azure instructions](https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-portal#create-a-private-endpoint) for details on creating a private endpoint to an endpoint service.
   Use [the service aliases for your region](#ec-private-link-azure-service-aliases). Select the **Connect to an Azure resource by resource ID or alias** option. For example for the region `eastus2` the service alias is `eastus2-prod-002-privatelink-service.64359fdd-7893-4215-9929-ece3287e1371.eastus2.azure.privatelinkservice`
   <note>
   The Private Link endpoint is created in the `Awaiting Approval` state. We validate and approve the endpoints when you create the private connection policy using the Private Link `resource ID`, as described in the next section [Create a private connection policy](#ec-azure-allow-traffic-from-link-id).
   </note>
2. Create a DNS record.
   1. Create a private DNS zone.
   Refer to the **Azure Private Link Service Alias** column in the [Azure Private Link Service aliases](#ec-private-link-azure-service-aliases) table for the name of the zone. For example, in `eastus2`, use `privatelink.eastus2.azure.elastic-cloud.com` as the zone domain name. Using this zone domain name is required to ensure certificate names match.
2. After creating the private DNS zone, associate the zone with your VNet by creating a [virtual network link](https://learn.microsoft.com/en-us/azure/dns/private-dns-getstarted-portal).
3. Create a DNS A record pointing to the private endpoint. Use `*` as the record name, `A` as the type, and put the private endpoint IP address as the record value.
   Follow the [Azure instructions](https://docs.microsoft.com/en-us/azure/dns/private-dns-getstarted-portal#create-an-additional-dns-record) for details on creating an A record which points to your private endpoint IP address.
   <tip>
   The private endpoint IP address is available through the network interface for the private endpoint.
   </tip>


## Create a private connection policy

After you create your private endpoint and DNS entries, you can create a private connection policy in Elastic Cloud.
Follow these high-level steps to add a private connection policy that can be associated with your deployments.
1. [Find your private endpoint resource name](#ec-find-your-resource-name).
2. [Find your private endpoint resource ID](#ec-find-your-resource-id).
3. [Create policies using the Private Link Endpoint resource ID](#create-private-connection-policy).
4. [Test the connection](#test-the-connection).
5. [Associate the private endpoint with your deployment](#associate-private-connection-policy).


### Find your private endpoint resource name

1. Go to your Private Link Endpoint in the Azure Portal.
2. Select **JSON View**.
3. Copy the value of the top level **name** property.


### Find your private endpoint resource ID

1. Go to your Private Link Endpoint in the Azure Portal.
2. Select **JSON View**.
3. Copy the value of the **properties.resourceGUID** property.

![Private endpoint JSON view](https://www.elastic.co/docs/deploy-manage/images/cloud-ec-private-link-azure-json-view.png)

![Private endpoint properties](https://www.elastic.co/docs/deploy-manage/images/cloud-ec-private-link-azure-properties.png)


### Create a policy using the Private Link Endpoint resource

When you have your private endpoint name and ID, you can create a private connection policy.
<note>
  The Private Link connection will be approved automatically after the private connection policy is created.
</note>

1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Select **Private connection**.
2. Select the resource type that the private connection will be applied to. Currently, only hosted deployments are supported.
3. Select the cloud provider and region for the private connection.
   <tip>
   Private connection policies are bound to a single region, and can be assigned only to deployments in the same region. If you want to associate a policy with resources in multiple regions, then you have to create the same policy in all the regions you want to apply it to.
   </tip>
4. Under **Connectivity**, select **PrivateLink**.
5. Enter your private endpoint **Resource name** and **Resource ID**. When applied to a deployment, this information will be used to filter traffic.
   <tip>
   You can apply multiple policies to a single deployment. The policies can be of different types. In case of multiple policies, traffic can match any associated policy to be forwarded to the resource. If none of the policies match, the request is rejected with `403 Forbidden`.[Learn more about how network security policies affect your deployment](https://www.elastic.co/docs/deploy-manage/security/network-security-policies).
   </tip>
6. Optional: Under **Apply to resources**, associate the new private connection policy with one or more deployments. After you associate the filter with a deployment, it starts filtering traffic.
   <tip>
   Associating the private connection policy with deployments is optional. After the private connection policy is created, private connectivity is established.Associating the policy with your deployments allows you to do the following:
   - [View a list of the resources](/docs/deploy-manage/security/network-security-policies#protected-resources-overview) that have private connections applied.
   - Filter traffic to your deployment.
   </tip>
7. To automatically attach this private connection policy to new deployments, select **Apply by default**.
8. Click **Create**.
9. Optional: You can [claim your Private Endpoint resource name and ID](https://www.elastic.co/docs/deploy-manage/security/claim-private-connection-api), so that no other organization is able to use it in a private connection policy.

Creating the policy approves the Private Link connection.
After the private link connection is approved, you can optionally [test the connection](#test-the-connection), and then [associate the policy](#associate-private-connection-policy) with your deployment.

### Test the connection

After you create your private connection, you can check that you're able to reach a cluster over Private Link.
Use the following URL structure. This URL is built from endpoint information retrieved from your Elastic deployment or project and the private hosted zone domain name that you registered.
```
https://{{alias}}.{{product}}.{{private_hosted_zone_domain_name}}
```

For example:
```text
https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com
```

<tip>
  You can use either 443 or 9243 as a port.You can also connect to the cluster using the Elasticsearch cluster or project ID, for example, https://6b111580caaa4a9e84b18ec7c600155e.privatelink.eastus2.azure.elastic-cloud.com.
</tip>

To test the connection:
1. If needed, find the endpoint of an application in your deployment:
   1. Log in to the [Elastic Cloud Console](https://cloud.elastic.co?page=docs&placement=docs-body).
   2. Under **Hosted deployments**, find your deployment.

   <tip>
   If you have many deployments, you can instead go to the **Hosted deployments** (Elastic Cloud Hosted) page. On that page, you can narrow your deployments by name, ID, or choose from several other filters.
   </tip>

   1. Select **Manage**.
   2. In the deployment overview, under **Applications**, find the application that you want to test.
   3. Click **Copy endpoint**. The value looks something like the following:

   ```text
   https://my-deployment-d53192.es.eastus2.azure.elastic-cloud.com
   ```

   In this endpoint, `my-deployment-d53192` is an alias, and `es` is the product you want to access within your deployment.
2. Test the setup using the following cURL command. Pass the username and password for a user that has access to the cluster. Make sure to replace the URL with your deployment's endpoint information and the private hosted zone domain name that you registered.
   ```sh
   $ curl -v https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243 -u {username}:{password}
   ```
   The output should look like this:
   ```sh
   * Rebuilt URL to: https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243/
   *   Trying 192.168.46.5...
   ..
   * SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
   * 	 server certificate verification OK
   * 	 common name: *.privatelink.elastic-cloud.com (matched)
   ..
       < HTTP/1.1 200 OK
   ..
   {
       "name" : "instance-0000000009",
       "cluster_name" : "fb7e805e5cfb4931bdccc4f3cb591f5f",
       "cluster_uuid" : "2cTHeCQYS2a0iH7YnQHrIQ",
       "version" : { ... },
       "tagline" : "You Know, for Search"
   }
   ```
   Check the IP address `192.168.46.5` it should be the same as the IP address of your private endpoint.
   The connection is established, and a valid certificate is presented to the client. Elastic responds, in the case of the Elasticsearch endpoint, with basic information about the cluster.

In the event that the Private Link connection is not approved by Elastic Cloud, you’ll get an error message like the following. Double check that the filter you’ve created in the previous step uses the right resource ID.
**Request**
```sh
$ curl -v https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243 -u {username}:{password}
```

**Response**
```sh
* Rebuilt URL to: https:/my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243/
*   Trying 192.168.46.5...
* connect to 192.168.46.5 port 9243 failed: No route to host
* Failed to connect to my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com port 9243: No route to host
* Closing connection 0
curl: (7) Failed to connect to my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com port 9243: No route to host
```


### Associate a private connection policy with a deployment

You can associate a private connection policy with your deployment from the policy's settings, or from your deployment's settings.
After you associate the policy with a deployment, it starts filtering traffic.
<tip>
  Associating the private connection policy with deployments is optional. After the private connection policy is created, private connectivity is established.Associating the policy with your deployments allows you to do the following:
  - [View a list of the resources](/docs/deploy-manage/security/network-security-policies#protected-resources-overview) that have private connections applied.
  - Filter traffic to your deployment.
</tip>


#### From a deployment

1. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
   On the **Hosted deployments** page, you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
2. On the **Security** page, under **Network security**, select **Apply policies** > **Private connection**.
3. Choose the policy you want to apply and select **Apply**.


#### From the policy settings

1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Find the policy you want to edit.
2. Under **Apply to resources**, associate the policy with one or more deployments.
3. Click **Update** to save your changes.


## Optional: Add an IP filter to allow SSO to Kibana from the Elastic Cloud console

When a private connection is applied to a deployment or project, you can't use SSO to log in to Kibana endpoints that are protected by private connections from the Elastic Cloud console. The connection to the Kibana public URL is still available.
As a workaround, you can add an IP filter for ingress traffic with the public IP address or addresses of the hosts that will use SSO through the Elastic Cloud console. You should scope your IP filter to the narrowest possible range: the egress IPs of your corporate VPN gateway, NAT gateway, or specific client machines.
If you don't create an IP filter, you might see an error like `Invalid SAML request` or `Forbidden due to traffic filtering`.
To add an IP filter:
1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Select **Create policy** > **IP filter**.
2. Select the resource type that the IP filter will be applied to: either hosted deployments or serverless projects.
3. Select the cloud provider and region for the IP filter.
4. Add a meaningful name and description for the IP filter.
5. Under **Access control**, select **Ingress**.
6. Add the public IP address or addresses of the hosts that will use SSO through the Elastic Cloud console.
7. Under **Apply to resources**, associate the IP filter with one or more deployments or projects.
8. Click **Create**.


## Access the deployment over a Private Link

For traffic to connect with the deployment over Azure Private Link, the client making the request needs to be located within the VNet where you’ve created the private endpoint. You can also setup network traffic to flow through the originating VNet from somewhere else, such as another VNet or a VPN from your corporate network. This assumes that the private endpoint and the DNS record are also available within that context. Check your service provider documentation for setup instructions.
<important>
  Use the alias you’ve set up as CNAME A record to access your deployment.
</important>

Use the following URL structure. This URL is built from endpoint information retrieved from your Elastic deployment or project and the private hosted zone domain name that you registered.
```
https://{{alias}}.{{product}}.{{private_hosted_zone_domain_name}}
```

For example:
```text
https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com
```

<tip>
  You can use either 443 or 9243 as a port.You can also connect to the cluster using the Elasticsearch cluster or project ID, for example, https://6b111580caaa4a9e84b18ec7c600155e.privatelink.eastus2.azure.elastic-cloud.com.
</tip>

To access the deployment:
1. If needed, find the endpoint of an application in your deployment:
   1. Log in to the [Elastic Cloud Console](https://cloud.elastic.co?page=docs&placement=docs-body).
   2. Under **Hosted deployments**, find your deployment.

   <tip>
   If you have many deployments, you can instead go to the **Hosted deployments** (Elastic Cloud Hosted) page. On that page, you can narrow your deployments by name, ID, or choose from several other filters.
   </tip>

   1. Select **Manage**.
   2. In the deployment overview, under **Applications**, find the application that you want to test.
   3. Click **Copy endpoint**. The value looks something like the following:

   ```text
   https://my-deployment-d53192.es.eastus2.azure.elastic-cloud.com
   ```

   In this endpoint, `my-deployment-d53192` is an alias, and `es` is the product you want to access within your deployment.
2. Send a request:
   **Request**
   ```sh
   $ curl -v https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243 -u {username}:{password}
   ```
   **Response**
   ```sh
   * Rebuilt URL to: https://my-deployment-d53192.es.privatelink.eastus2.azure.elastic-cloud.com:9243/
   *   Trying 192.168.46.5... 
   ..
   * SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
   * 	 server certificate verification OK
   * 	 common name: *.privatelink.elastic-cloud.com (matched)
   ..
       < HTTP/1.1 200 OK
   ..
   {
       "name" : "instance-0000000009",
       "cluster_name" : "fb7e805e5cfb4931bdccc4f3cb591f5f",
       "cluster_uuid" : "2cTHeCQYS2a0iH7YnQHrIQ",
       "version" : { ... },
       "tagline" : "You Know, for Search"
   }
   ```


### Azure Private Link and Fleet

If you are using Azure Private Link together with Fleet, and enrolling the Elastic Agent with a private connection URL, you need to configure Fleet Server to use and propagate the Azure Private Link URL by updating the **Fleet Server hosts** field in the **Fleet settings** section of Kibana. Otherwise, Elastic Agent will reset to use a default address instead of the Azure Private Link URL.
The URL needs to follow this pattern:
```text
https://{{fleet_component_ID_or_deployment_alias}}.fleet.{{private_hosted_zone_domain_name}}:443`
```

Similarly, the Elasticsearch host needs to be updated to propagate the private connection URL. The Elasticsearch URL needs to follow this pattern:
```text
https://{{elasticsearch_cluster_ID_or_deployment_alias}}.es.{{private_hosted_zone_domain_name}}:443
```

The settings `xpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.outputs` that are needed to enable this configuration in Kibana are not available in the Kibana settings in Elastic Cloud.

## Setting up an inter-region Private Link connection

Azure supports inter-region Private Link as described in the [Azure documentation](https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview).
This means your deployment on Elastic Cloud can be in a different region than the Private Link endpoints or the clients that consume the deployment endpoints.
![Inter-region Private Link](https://www.elastic.co/docs/deploy-manage/images/cloud-ce-azure-inter-region-pl.png)

1. Set up Private Link Endpoint in region 1 for a deployment hosted in region 2.
   1. Create your Private Link Endpoint using the service alias for region 2 in the region 1 VNET (let’s call this VNET1).
2. Create a Private Hosted Zone for region 2, and associate it with VNET1 similar to the step [Create a Private Link endpoint and DNS](#ec-private-link-azure-dns). Note that you are creating these resources in region 1, VNET1.
2. [Create a private connection policy](#create-private-connection-policy) in the region where your deployment is hosted, and [associate it](#associate-private-connection-policy) with your deployment.
3. [Test the connection](#ec-azure-access-the-deployment-over-private-link) from a VM or client in region 1 to your Private Link endpoint, and it should be able to connect to your Elasticsearch cluster hosted in region 2.


## Manage private connection policies

After you create your private connection policy, you can edit it, remove it from your deployment, or delete it.

### Edit a private connection policy

You can edit a policy's name, description, VPC endpoint ID, and more.
1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Find the policy you want to edit, then click the **Edit** `pencil` button.
2. Click **Update** to save your changes.

<tip>
  You can also edit network security policies from your deployment's **Security** page or your project's **Network security** page.
</tip>


### Remove a private connection policy from your deployment

If you want to remove a specific policy from a deployment, or delete the policy, then you need to disconnect it from any associated deployments first. You can do this from the policy's settings, or from your deployment's settings. To remove an association through the UI:

#### From your deployment

1. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
   On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
2. On the **Security** page, under **Network security**, find the policy that you want to disconnect.
3. Under **Actions**, click the **Delete** icon.


#### From the private connection policy settings

1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Find the policy you want to edit, then click the **Edit** `pencil` button.
2. Under **Apply to resources**, click the `x` beside the resource that you want to disconnect.
3. Click **Update** to save your changes.


### Delete a private connection policy

If you need to remove a policy, you must first remove any associations with deployments.
To delete a policy:
1. Log in to [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
2. From the navigation menu, select **Security** > **Network security**.

1. Find the policy you want to edit, then click the **Delete** button. The icon is inactive if there are deployments associated with the policy.