Summary

  • 2 minutes

Your company wanted to learn how they could use their existing expertise in Maven to automate deployment of their Java web apps to Azure App Service. To test the ease with which your company could use the Maven Plugin for Azure App Service, you used the following steps:

  1. You created a sample web app with a Maven archetype, and you tested it locally using Tomcat.

  2. Once you verified that your application was working successfully, you added the Maven Plugin for Azure App Service to your project and configured it interactively.

  3. After you configured the Maven Plugin for Azure App Service, you deployed your web app to Azure App Service and tested it in the cloud.

  4. You updated your web app, redeployed it to Azure App Service, and tested it in the cloud.

  5. You learned about the various methods that you can use to authenticate your deployments for automation.

The whole process would be difficult to achieve without the Maven Plugin for Azure App Service. You'd need to manually create an App Service plan and manually configure Maven to transfer your application over FTP to Azure App Service.

Now that you've learned how to use the Maven Plugin for Azure App Service, you're confident that you can recommend migrating your Java application code to Azure. You know your team can continue using Maven to manage projects and deploy them to Azure.

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources that you leave running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Learn more

The following links discuss additional information related to Java development on Azure:

These links provide a wealth of information about getting started with Apache Maven: