Thanks for the info.. As we are in the testing phase, JAMF is not enrolled into production environment.
Please help in providing the inputs of below queries
1. What all the changes should be made when we change the cloud host name (JAMF URL) ?
2. What will be the impact on the current setup ?
When you change the name of the URL that you're devices are supposed to trust, they need to re-learn how to trust that server since it will then be unrecognized. In a nutshell, anything you've enrolled will need to be re-enrolled. If you're in a testing phase the impact should hopefully be minimal, but if you're making this change while managing active devices you basically have to treat it like migrating MDMs.
Making this decision early on in your evaluation/testing phase will help prevent pain later. Though that being said, pick something you're happy with that won't need to change.
If you go with a dedicated hosted (jamfcloud) solution with premium support/services you can actually use a custom domain name of your choosing, like something that matches your organization's domain name(s). Depending on the size/scope of your deployment that may or may not be worth the extra investment.
Just to iterate what everyone else had commented on.
It'll break your existing devices, you'll have to plan a migration to a different MDM instance either by remote wipe and DEP or remove the old MDM profile and user initiated enrolment to the new MDM