---
title: "Validating and Accepting Configuration for PayGo Instance"
canonical: "https://docs.infoblox.com/space/vniosazure/880476175/Validating%20and%20Accepting%20Configuration%20for%20PayGo%20Instance"
format: markdown
---
After you save the VM configuration, you can view the information in the *Review + Create* panel. If you need to change any configuration, you can return to **Configure** **VM** **settings**. Click **Create** to accept the configuration and create the instance.

*Viewing VM Summary*

![Review.png](media://46056c03-64e5-4602-95fa-4ca333f570a2)

 

## vNIOS PayGo Configuration Guidelines

- PayGo instances cannot be switched to non-PayGo instances.
- PayGo instances are licensed immediately upon launch, and the licenses remain in force as long as the customer continues to pay for the instance.
- Downgrades are not allowed for PayGo instances below NIOS 9.0.5.
- If there are Temporary licenses in cloud-init data, they will be skipped during configuration.
- Restoring AWS/Azure snapshots, AMIs, or images for PayGo instances is generally not recommended.
- If a PayGo instance lacks sufficient resources and does not meet the minimum requirements, it will fail to boot into NIOS, and an error message will be displayed on the console.If a PayGo instance does not meet the required CPU or memory specifications, NIOS will fail to start, triggering an error message indicating insufficient resources.
- If the memory or CPU configuration of a PayGo instance is altered from the original NIOS model, the instance will not start, and an error message regarding a NIOS license mismatch will be triggered on the console.