# Resize existing VAs in ISC

**URL:** <https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [July 16, 2026, 4:27pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660 "2026-07-16T16:27:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prashanth1812](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Prashanth1812](https://developer.sailpoint.com/discuss/u/Prashanth1812)\
**Post date:** [July 16, 2026, 4:27pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/1 "2026-07-16T16:27:22Z")

</div>

Hi all,

We are considering resizing our existing Azure-hosted VAs. Is that an option? If so, do you have a step-by-step process for scaling them without impacting the existing configuration (e.g., ISC registration)? Also, since we have two VAs, should they be resized one at a time?

Standard\_D8s\_v5

x86 Processors: 4  
Memory: 32 GB  
Storage: 128 GB

#### ===== Our Virtual Appliance Specs =====

CPU(s): 4  
On-line CPU(s) list: 0-3  
Model name: Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz  
CPU(s) scaling MHz: 125%  
NUMA node0 CPU(s): 0-3  
Mem: 15Gi 3.8Gi 7.6Gi 1.1Mi 4.5Gi 11Gi  
Filesystem Size Used Avail Use% Mounted on  
/dev/sda9 122G 8.9G 108G 8% /

---

<div class="post-metadata">

**Author:** ![HussainshaSyed001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/hussainshasyed001/32/28234_2.png) [@HussainshaSyed001](https://developer.sailpoint.com/discuss/u/HussainshaSyed001)\
**Post date:** [July 16, 2026, 4:44pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/2 "2026-07-16T16:44:23Z")

</div>

my recommendation would be creating new VAs as per your desired config and it is the best choice

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [July 16, 2026, 4:54pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/3 "2026-07-16T16:54:25Z")

</div>

You should talk to your systems/network admin guys as you will have to reconfigure the Virtual Machine itself.

And, I do not think creating a new VAs and deleting old ones that @HussainshaSyed001 suggested is a good idea. Sorry to disagree

---

<div class="post-metadata">

**Author:** ![othornewill](https://avatars.discourse-cdn.com/v4/letter/o/a6a055/32.png) [@othornewill](https://developer.sailpoint.com/discuss/u/othornewill)\
**Post date:** [July 17, 2026, 6:55am UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/4 "2026-07-17T06:55:32Z")

</div>

> [@Prashanth1812](#):
>
> Standard\_D8s\_v5

I have resized my Azure VAs in the test-environment multiple times. It’s pretty simple, you just need to deallocate the VM, resize the machine and start. This bash script is what I would use, with the Azure CLI. Perhaps it helps.

I’d recommend you see how it works in your test-environment first, in case my script is bad after all. Haven’t used it in over a year now.

```bash
#!/bin/bash

# ======================================
# Define all necessary variables here
# ======================================
RESOURCE_GROUP="my-resource-group" # Replace with your Resource Group name
VM_NAME="sailpoint-va01" # Replace with your VM name
LOCATION="eastus" # Region where your VM is deployed
NEW_SIZE="Standard_B2ms" # Desired VM size: 

# ======================================
# Begin the resize process
# ======================================
echo "Starting the resize process for VM '$VM_NAME' in Resource Group '$RESOURCE_GROUP' located in '$LOCATION'..."

# Step 1: Deallocate the VM (required for resizing)
echo "Deallocating the VM..."
az vm deallocate --resource-group "$RESOURCE_GROUP" --name "$VM_NAME"

# Step 2: Resize the VM to the new size
echo "Resizing the VM to size '$NEW_SIZE'..."
az vm resize --resource-group "$RESOURCE_GROUP" --name "$VM_NAME" --size "$NEW_SIZE"

# Step 3: Start the VM after resizing
echo "Starting the VM..."
az vm start --resource-group "$RESOURCE_GROUP" --name "$VM_NAME"

echo "Resize process completed. The VM '$VM_NAME' is now set to '$NEW_SIZE'."

```

---

<div class="post-metadata">

**Author:** ![Prashanth1812](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Prashanth1812](https://developer.sailpoint.com/discuss/u/Prashanth1812)\
**Post date:** [July 17, 2026, 11:25am UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/5 "2026-07-17T11:25:04Z")

</div>

@iamnithesh when you say re-configure, existing configurations will be lost like registration/FW and all other stuff?

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [July 17, 2026, 1:01pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/6 "2026-07-17T13:01:27Z")

</div>

No, I meant to say reconfigure the “VM” itself. Not the VA. There should not be any changes to the VA.

Response from @othornewill seems like what you need

---

<div class="post-metadata">

**Author:** ![Prashanth1812](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@Prashanth1812](https://developer.sailpoint.com/discuss/u/Prashanth1812)\
**Post date:** [July 17, 2026, 1:29pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/7 "2026-07-17T13:29:03Z")

</div>

Hi @othornewill Thanks for the response. I’ll test this in our TEST environment and see how it works. I’ll post an update here. Thanks

---

<div class="post-metadata">

**Author:** ![BBR1](https://avatars.discourse-cdn.com/v4/letter/b/c57346/32.png) [@BBR1](https://developer.sailpoint.com/discuss/u/BBR1)\
**Post date:** [July 17, 2026, 3:04pm UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/8 "2026-07-17T15:04:54Z")

</div>

Yes,

Existing Azure-hosted SailPoint VA can be resized without redeploying them. Stop the VM, resize it, and start it again. In a 2-VA cluster, resize one VA at a time to avoid downtime. Existing VA registration and configuration remain intact because the VM disk is preserved during the resize operation. Always validate the change in a test environment before applying it to production.

---

<div class="post-metadata">

**Author:** ![schattopadhy](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/schattopadhy/32/8854_2.png) [@schattopadhy](https://developer.sailpoint.com/discuss/u/schattopadhy)\
**Post date:** [July 18, 2026, 1:39am UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/9 "2026-07-18T01:39:22Z")

</div>

@Prashanth1812

Follow the below steps

- Work with devops to build those new servers
- Create a new cluster
- Connect your new virtual appliances to that cluster
- Migrate all the apps to the new cluster
- Decomission the old VA and cluster once all apps are migrated

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [September 16, 2026, 1:39am UTC](https://developer.sailpoint.com/discuss/t/resize-existing-vas-in-isc/216660/10 "2026-09-16T01:39:28Z")

</div>

Closed on September 16, 2026, 1:39am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
