I created a new app service plan, identical to an existing one (the only way to rename a plan). But it won't let me assign app services to it. Why?
Same region & plan.
thanks - dave
I created a new app service plan, identical to an existing one (the only way to rename a plan). But it won't let me assign app services to it. Why?
Same region & plan.
thanks - dave
@DavidThielen-3337 Thanks for reaching out. In addition to being in the same region, the source and target plans should be in the same resource group as well. Is that true in your case?
@DavidThielen-3337 You can move an app to another App Service plan, as long as the source plan and the target plan are in the same resource group and geographical region.
To elaborate, Azure deploys each new App Service plan into a deployment unit, internally called a webspace. Each region can have many webspaces, but your app can only move between plans that are created in the same webspace. All plans created with the same resource group and region combination are deployed into the same webspace.
For example, if you created a plan in resource group A and region B, then any plan you subsequently create in resource group A and region B is deployed into the same webspace. (Note that plans can’t move webspaces after they’re created, so you can’t move a plan into “the same webspace” as another plan by moving it to another resource group.)
Please refer to this article to know more: Move an app to another App Service plan
Hope this helps. Do let us know if you have further questions.
If an answer is helpful, please "Accept answer" and/or "Up-Vote" which might help other community members reading this thread.
Hi;
First off, sorry for the delay answering. I was on vacation.
All of this is in subscription ID ----***
It is in the same resource group. I am trying to move the 12SimpleSecrets app service to the App Service Plan SmallWebsites
Both are in the resource group Thielen_Websites and Location West US.
??? - thanks - dave
@DavidThielen-3337 Apologies for not getting back sooner here. Just to clarify, are you not able to find the expected ASP when trying to initiate the move from the Change App Service plan blade? Or is the operation resulting in an error when attempted?
Since it appears like you're not able to move your app to an existing App Service plan, I'd request you to please try the following:
Navigate to the app that you want to move on the Azure Portal
From the left menu, select Change App Service plan
Create a new plan manually by selecting Create new
Select the pricing tier of the new plan, or proceed with the default
When done, click OK

Please check if that helps. Do let me know what you see.
Hi bhargaviannadevara-msft;
First off, no reason to apologize for the delay. I was slow to get back to you (I was on vacation).
Second, I want to figure this out rather than create a new App Service Plan. Here is my app service plan:

Resource group: Thielen_Websites
Location: West US
Pricing tier: D1:shared
Here is the App Service:

Resource group: Thielen_Websites
Location: West US
App Service Plan: Default 1 (D1: Shared)
When I go to change the App Service Plan - it does not show the App Service plan SmallWebsites as an option:

Any idea why not?
thanks - dave
@DavidThielen-3337 Thanks for taking the time to report this issue. Summarizing the outcome of the offline investigation here so it helps others in the community as well.
To work around the issue, you can clone your existing App Service app to a newly created app in the same region selecting the desired App Service Plan.
Steps to clone your App Service app:
Navigate to your app on the Azure Portal and look for the Clone App option under the Development Tools section
When cloning the app, make sure you select the desired values for the app name (cannot be the same as the previous app), resource group and App Service plan (choose the desired ASP)
Click on Create
The above can also be performed with some Azure PowerShell cmdlets. Check this article for more details: Azure App Service App Cloning Using PowerShell
Hope this helped you get around the issue. Do let us know if you have further questions.
If an answer is helpful, please "Accept answer" and/or "Up-Vote" which might help other community members reading this thread.
Hello.
We are facing the same issue with some migrations.
@bhargaviannadevara-msft thanks a lot for a workaround. Is there any chance Azure will fix this bug or an official solution is to use workarounds?
Thanks a lot for your answers in advance
Looks like we've found a solution.
It appears ability to move resources between service plans depends on something called "webspace" which you can not define by yourself but it is possible to ensure you deploy service plan to the same webspace.
ToDo:
- check json of service plan you want to move and check for the resource group defined in a webspace ( it might be different than an actual resource group plan is currently in if plan was previously moved )
- create new service plan in the same group that is defined in a webspace attribute ( region must be the same )
- move service plan to the group you want it to be in
Once you create plan under "correct" webspace you can move it whenever you want as webspace parameter won't change anymore.
The app should see the new plan listed after that's done
7 people are following this question.