This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 52%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
I am trying to add a new Resource (the WordPress App Service) to an existing App Service Plan, but am only given the option to create a new App Service Plan.
Here are the steps taken. I click the + button on the Azure portal home page to Create A Resource, select the App Service, select the correct (existing) Resource Group and confirm that the region for the App Service is the same as for the Resource Group, and fill out the details, but when I get to the "Review + create" screen it indicates that the new App Service will be put into a new App Service Plan. There is no option that I can see to select an existing App Service Plan.
How can I add this App Service to the existing Plan?
Hi, @Gurs
Unfortunately, the WordPress App Service template doesn't seem to have an option to add to an existing App Service plan.
You have a way to move an App Service to an existing App Service plan after deploying to a new App Service plan.
try it.
And if you have any questions please let us know again.
Thanks @Takahito Iwasa , I had a feeling that would be the fallback approach. We ended up cloning an existing site in the App Service Plan and then changing the databases, which was probably more work than deploying to a new ASP and moving it to the existing ASP.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Gurs-7768, Thanks for the update. Adding to TakahitoIwasa suggestions to share additional info.
As posted by ElliottHamai-6773 (from App Service product team) on this discussion thread.
“We recently pushed out a change to the WordPress on App Service creation experience which simplifies the configuration for WordPress. In the old experience you needed to specify database information, but in the new experience that is no longer required. Instead, we now choose a configuration that we know will work well for you to run WordPress with the least amount of issues.”
The reasoning for this change was to enable production scenarios and make the experience simpler to get started. I completely understand about the cost effects here, that said, you may try the following options post creation of your resources:
• The App Service plan can be scaled down to a different SKU | post creation.
• The WebApp can be moved to a different App Service Plan | post creation.
• You may generate an ARM template from your WordPress deployment and further tweak it to fit your needs.
Please be assured that we have also relayed your feedback to our product engineering internally.
Thanks for your cooperation and patience!