Best Practices for Changing the IP Scheme for a MyCloudIT Deployment

Rob Waggoner

Smiling teacher showing something on screen to mature student in the computer room

One of the benefits of using MyCloudIT to deploy your RDS deployments is consistency.  While consistency is very good, sometimes we need things to be a little inconsistent so everything can remain consistent. The networking infrastructure is a good example of something that may need to change to continue to grow your platform. Please, as a rule, do not change the resource names or configuration of resources created by MyCloudIT. Our automation leverages the consistency of our deployments to provide ongoing management and insights. Changing items like VM or collection names will break our automation. 

When MyCloudIT creates a new deployment, every deployment is created using the same Azure Virtual Network IP scheme ( If you are going to connect our RDS deployment to an existing network that already uses the IP scheme (, that could pose a problem. Usually it is easier to change the IP scheme of the new MyCloudIT deployment, then to change your existing infrastructure to mesh with our new infrastructure. Currently, there is not a way to choose the IP scheme during the creation of a new MyCloudIT deployment, but if you are using a Domain Joined deployment, there is the option to choose which subnets the new resources are deployed into. But again, new deployments do not offer this capability. But if you need to change an IP scheme of a deployment, we’ve got you covered. Just open a support ticket and tell us the name of the deployment to change, and your preferred IP scheme, and we will take care of it.  Of course, changing the IP scheme will cause an outage, typically the outage is less than an hour, but this action is something that needs to be planned.

Originally, I was going to dig into the details of how to change the IP scheme of your infrastructure, but it is a very in-depth process and requires an understanding of your infrastructure.  Instead of trying to document all the possible scenarios, our support team put together some automation to make the process easier. In the future, we plan to fully automate this process, but for now, just reach out to our support team, by opening a ticket within your subscription and they will explain what they will do, and then take care of your deployment. 

Want Future Best Practices Delivered Right to Your Inbox?
Subscribe to Our Blog