This year, Microsoft Build is entirely online. Live and pre-recorded sessions are available for anyone to view. This article is a recap of the sessions from the App Service team, along with links to more information.
Building and Managing .NET Core with App Service
Building web apps with .NET Core? Check out the latest from the App Service team including how to build a continuous delivery pipeline using GitHub Actions, how to use Event Grid to subscribe and act on deployment events and how to monitor your production apps with Health Checks.
GitHub Actions is a flexible automation framework that allows developers to (among other things) continuously deploy their applications to App Service.
App Service Health Checks
App Service Health Checks will automatically remove and restart unhealthy instances of your application when you are scaled out.
Event Grid Integration
Event Grid is a high performance publish/subscribe messaging system. App Service now emits events that can be handled with Functions, Logic Apps, and more.
Migrate Applications to Azure App Service
See how Azure is making it easy to quickly get your application running on App Service. We’ll show you how to use Migration Assistant for moving IIS sites and Linux containers to the cloud.
Many of you attended our “Ask the Experts” live session and sent us your questions. Here are some common questions you asked, along with their answers.
- Can you use LetsEncrypt certificates with Azure App Services? You’re still able to use Let’s Encrypt certs with App Service, however there is no official support when it comes to integrating it with auto-renew. We have App Service Managed Certificates, which is our free certificate offering that supports auto-renew. This feature is currently in preview and only currently supports CNAME Records. Documentation.
- What is the status for App Service Managed Certificates supporting apex/naked domains? This is the next milestone for this feature that we are currently working on. We don’t have an ETA to provide as of now.
- Is it a good strategy to use deployment slots to define environments (eg. myapp, myapp/uat, myapp/qa) or would it be better to have different resources for each environment? Would it affect the performance of the main prod “myapp” service? You can certainly use slots to stage your test, QA, and other environments. This works especially well if your team uses the Gitflow branching strategy, as each branch can be continuously deployed to a staging slot. If you are worried about the extra slots consuming too many resources, you can actually host the production slot on it’s own, independent App Service Plan.
- What is the status for the different logs with the Azure Monitor integration? We will be releasing AppServiceAppLogs for Windows soon – estimating the next two/three months. We don’t have an ETA for the other logs as of now.