See the list of supported regions before deployment to confirm Everpure Cloud Dedicated availability.
Note: When deploying Everpure Cloud Dedicated in Italy North and Canada East regions, using Azure Portal may lead to deployment of an incorrect SKU, e.g. MU-R1 instead of MP2-R2. Please use other deployments methods for deploying MP2-R2 SKUs, like Bicep or Terraform.
To deploy Everpure Cloud Dedicated using the Terraform, see steps in this KB article.
To deploy Everpure Cloud Dedicated using the Azure CLI, see steps in this KB article.
Note: The followings steps reflects deployment of Everpure Cloud Dedicated versions 6.1.4 or higher which no longer deploys a public load balancer. Therefore it is mandatory that there is internet access for the Everpure Cloud Dedicated system network interface in order to successfully deploy. See the section within the prerequisites KB article.
Follow the steps below to deploy Everpure Cloud Dedicated:
1. Log into the Azure portal and open Azure Marketplace.
2. In the Marketplace search bar, search for “pure storage cloud”.
3. Click on the Everpure Cloud Dedicated (Product Deployment) tile. Note that the subscription listing is used for purchasing licenses only.
4. Select a version you would like to deploy under Create dropdown.
5. Complete the required fields. An example screenshot is provided for additional guidance below.
a. Select the desired Subscription.
b. Select the desired Resource group in which you want the Everpure Cloud Dedicated managed application to reside.
c. Select the desired Region you want to deploy your Everpure Cloud Dedicated managed application.
It is highly suggested that this region matches the region of your Resource Group in selection b. The deployment may occasionally fail if they do not match.
d. Select the desired Pure Storage Cloud Dedicated model.
e. Select the desired Availability Zone.
Some zones may not have the required Azure backend storage available, which is required for Everpure Cloud Dedicated. To find out which zone in your specific Azure subscription has Ultra SSDs (for MU-R2 Everpure Cloud Dedicated models) or Premium V2 SSD (for MP2-R2 Everpure Cloud Dedicated models), run the following command from the Azure CloudShell or locally with Azure login to your subscription:
For Ultra SSDs (for MU-R2 Everpure Cloud Dedicated models)
- Azure PowerShell
Get-AzComputeResourceSku | where {$_.ResourceType -eq “disks” -and $_.Name -eq “UltraSSD_LRS”}
- Azure CLI
az vm list-skus --resource-type disks --query "[?name=='UltraSSD_LRS'].{Region:locationInfo[0].location, Zones:locationInfo[0].zones}"Premium V2 SSD (for MP2-R2 Everpure Cloud Dedicated models)
- Azure PowerShell
Get-AzComputeResourceSku | where {$_.ResourceType -eq “disks” -and $_.Name -eq “PremiumV2_LRS”}- Azure CLI
az vm list-skus --resource-type disks --query "[?name=='PremiumV2_LRS'].{Region:locationInfo[0].location, Zones:locationInfo[0].zones}"f. Enter the desired Array Name for the Everpure Cloud Dedicated VM instance.
g. Enter your Company Domain Name. This can be changed later.
Example: purestorage.com
h. Enter the Everpure Cloud Dedicated License key.
g. (Optional) Enter comma separated email addresses of recipients who wish to receive Purity alerts.
h.
(Optional) If you wish to log in via SSH with the default pureuser username, an SSH public key
can be provided here.
Alternatively, after deployment you can also log into the Pure Storage Cloud Dedicated GUI (HTTPS) and manually add the SSH key to the desired user login.
i. (Optional) If you intend to use this Everpure Cloud Dedicated Array with Fusion, check this box.
j. Enter the desired Application Name of your Everpure Cloud Dedicated managed application.
k. (Optional) You can change the name of the Managed Resource Group if desired.
Example:
6. Click Next: Managed Identity.
Enter the User Assigned Identity Resource Id created for the array. The steps on how to create, assign roles, and get the resource Id are under Prerequisites section, Azure Security Requirements - User Managed Identity.
7. Click Next: Network.
Complete the Network fields. Everpure Cloud Dedicated has four network interfaces (system, management, iSCSI, replication) and will need a Virtual Network (VNet) and subnet assigned.
- You must select the same VNet for all four interfaces. However, the interfaces can reside in the same or different subnet within the VNet. See the Networking Prerequisites article for network option diagrams in the prerequisites document.
- Ensure the subnet you select for the System interface has internet access. Example via NAT Gateway or Azure Firewall. See network Internet Access section in the prerequisites document for options to configure internet access.
8. Starting with Everpure Cloud Dedicated version 6.8.7 and higher, you can select initial raw array capacity and enable/disable Automatic Capacity Upgrade feature during the deployment.
If you are deploying Everpure Cloud Dedicated version 6.8.7 or higher, click Next: Capacity.
Select if you want to enable/disable Automatic Capacity Upgrade(for information about this feature please read details here).
Select the initial raw capacity of Pure Storage Cloud Dedicated Array. You can choose from several capacity points based on what SKU model are you deploying. For detail about available capacity point please read here.
9. Click Next: Tags.
Add any desired tags for this deployment.
10. Click Next: JIT Configuration.
Ensure that you select Yes to enable Just in Time (JIT) remote access.
For Everpure Cloud Dedicated version 6.5.1 and above is the enablement of this feature strongly RECOMMENDED
For Everpure Cloud Dedicated version 6.5.0 and below is the enablement of this feature MANDATORY
In order to bolster the security of your deployed resources from the Azure Marketplace, we recommend enabling the Just-In-Time (JIT) Access feature with manual approval mode. JIT Access puts you in control, ensuring that no one, including us as your service provider, can access your resources without your prior approval.
JIT Access, when enabled and configured with manual approval, effectively restricts the service provider's default full access to a read-only access. This applies even in cases where the customer lacks a Microsoft Entra ID P2 license.
You cannot disable/enable JIT feature after deployment, so it is very important that it is enabled during the deployment. The JIT Configuration (approval mode, duration, approvers) can be changed later.
Click on the Customize JIT configuration button. Switch the Approval mode to Manual value.
Select Manual mode.
Click Add Approver.
Click on the Customize JIT configuration button. Switch the Approval mode to Manual value.
On the right-hand side, search and select user(s)/group(s) whom you wish to be approvers for JIT requests from Pure Support.
We recommend designating a Microsoft Entra security group, which includes several users responsible for deployed resources, as the Approvers.
Click Select and Save.
11. Click Next: Review + create.
Read and check the box to acknowledge the terms and conditions.
12. Review your parameters and click Create.
Everpure Cloud Dedicated will now be deployed into your desired Resource group, VNet, and subnets. The deployment should be completed within 20 minutes depending on the region.
Note: It may take a few minutes after deployment completes for the Everpure Cloud Dedicated to initialize and be ready.
The previous steps provided a guidance on deploying an Everpure Cloud Dedicated managed application using the the Azure Portal GUI.
To deploy Everpure Cloud Dedicated using the Terraform, see steps in this KB article.
To deploy Everpure Cloud Dedicated using the Azure CLI, see steps in this KB article.
Optional: To prevent accidental deletion of Everpure Cloud Dedicated Managed Application, consider using Azure Locks. Guide for that can be found here.