Hello, @Leonel MB ! Most of this will boil down to making sure that the new ISP connection is both reliable (at all times of day) and fast enough (bandwidth and ping) to meet your needs. I'll go into more detail below.
What should I take into consideration on Azure when changing internet service providers (ISPs)?
- Network connectivity: You'll want to make sure that your ISP provides reliable and fast network connectivity for any local resources or data that may need to transit to or from Azure networks. This is especially important when considering RDP demands for VM connections, VHD or other large volumes of VM related data that you may have locally, and is working as needed even during peak traffic hours.
- Azure Peering Service partners for enterprise: Azure Peering Service is a networking service that enhances the connectivity to Microsoft cloud services such as Microsoft 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet. Microsoft has partnered with internet service providers (ISPs) worldwide to provide reliable and high-performing public connectivity with optimal routing from the customer to the Microsoft network.
- Local/on-premises network settings may change: When changing ISPs, you'll also want to confirm that any existing connections you have on-premises that are used in hybrid environments, local dependencies, scripts, templates, or other setup/configuration files are updated (IP address, custom DNS settings, etc.).
I hope this has been helpful! Your feedback is important so please take a moment to accept answers.
If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!