You may need to move the resources associated with a stateful node to a different Azure subscription, for example when reorganizing accounts or transferring ownership. This process involves detaching the stateful node from Flexera management, moving the Azure resources, and then re‑importing the virtual machine.
The steps below explain how to complete this process safely while keeping the virtual machine running.
-
Prepare the stateful node for deallocation
In the Flexera console, go to Elastigroup > Stateful nodes, select the stateful node, and then select Actions > Edit configuration.
Go to Review, switch to JSON, and select Edit mode.
-
Prevent the node from reverting to Spot
In the
strategysection, setrevertToSpottoneverand confirm the preferred lifecycle is on‑demand.Example:
{ "strategy": { "fallbackToOd": true, "drainingTimeout": 120, "preferredLifecycle": "od", "revertToSpot": "never", "optimizationWindows": null } }Save and apply the configuration.
-
Recycle the stateful node
Recycle the stateful node so it runs as an on‑demand virtual machine.
-
Verify the node lifecycle
Confirm that the stateful node is no longer running on a Spot virtual machine.
-
Delete the stateful node from Flexera
Open Edit node and delete the stateful node.
In the Delete stateful node window, deselect all options.
This ensures the virtual machine and its resources are not deleted in Azure. -
Verify the resources in Azure
In the Azure portal, confirm that the virtual machine and all associated resources are running.
-
Move the Azure resources
Move the virtual machine and its related resources to the new Azure subscription using Azure resource move functionality.
-
Connect the new Azure subscription
In the Flexera console, connect the new Azure subscription.
-
Import the stateful virtual machine
Import the existing virtual machine as a stateful node in the new subscription.
Related Articles
Remove an Azure stateful node from Flexera and manage it in Azure 4Number of Views Increase disk size for Azure stateful nodes 5Number of Views Increase CPU, memory, or disk size for a stateful node on Azure 4Number of Views Understand how stateful node resources are deallocated when you delete an instance 3Number of Views Fix stateful node import or launch failures caused by disk redundancy and zone settings 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago