Communication between Everpure Cloud Dedicated and Azure Service Endpoints will occur over the Everpure Cloud Dedicated System interface.
Therefore, the Service Endpoints should be configured on the correlating subnet used the system interface.
Key Vault and Microsoft Storage Service Endpoint
- Log into the Azure Portal.
- Navigate to the subnet upon which the Everpure Cloud Dedicated system interface
resides.
Note: You can locate the subnet used by the Everpure Cloud Dedicated system interface by viewing the Parameters and Output tab on your Everpure Cloud Dedicated managed application.
- Set the appropriate Microsoft Storage and Key Vault service endpoints.
- Click on Subnets
- Click on the subnet used by the Everpure Cloud Dedicated system interface
- An Azure menu will appear on the right hand side. Select
Microsoft.KeyVaultandMicrosoft.Storageservices
-
Click OK
-
(optional) Endpoint Azure Blob Storage for CloudSnap
To enable Service Endpoints for Cloudsnap to Azure Blob Storage target, navigate to the subnet where the Everpure Cloud Dedicated replication interface resides, and set the service endpoint called
Microsoft.Storage
For deploying Everpure Cloud Dedicated version 6.8.1 and below
Before the Everpure Cloud Dedicated version 6.8.2, the Everpure Cloud Dedicated also contain a CosmosDB resource, requiring a service endpoint for this service. To deploy, please configure also a Service Endpoint for the
Microsoft.AzureCosmosDB
service on the system subnet.
The Service Endpoint for Azure CosmosDB is not required for deploying Everpure Cloud Dedicated version 6.8.2 and higher.