If not using a migrated service, you can read connection strings and app settings from the Configure tab of the Mobile Services section of the Azure classic portal. NET project for your application and publish it to your new site.Using a copy of your client application updated with the new URL, validate that everything works as expected.
Mobile Apps provides a new Mobile App Server SDK which provides much of the same functionality as the Mobile Services runtime.
First, you should remove all references to the Mobile Services packages. At this point you will have a project that no longer references Mobile Services SDKs. For this upgrade, most developers will want to download and install the package, as this will pull in the entire required set.
Instead, you should create a new mobile app that serves as a duplicate.
You can put this application on the same App Service plan to avoid incurring additional financial cost.
You will likely want to use the same database and Notification Hub as you did in Mobile Services.
You can copy these values by opening Azure portal and navigating to the original application, then click Settings .
Navigate to your new upgrade site and paste them in, overwriting any existing values.
Repeat this process for any other application settings your app needs.
If you have already migrated an existing mobile service, you will want to create this version on the same hosting plan.
Open the Azure portal and navigate to your migrated application.
App Service Mobile is a new way to build mobile applications using Microsoft Azure. If you need to upgrade a backend application, refer to Upgrading your Mobile Services.