An introduction to App Service Environment v3 | Azure Friday

The Azure App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for securely running App Service apps at high scale. Christina Compy joins Scott Hanselman to introduce ASE v3.
0:00 - Introduction
4:26 - Demo
8:39 - Resources
9:48 - ASEv3 vs ASEv2
13:19 - Wrap-up
🔗 App Service Environment overview - aka.ms/azfr/706/01
🔗 Create an App Service Environment - aka.ms/azfr/706/02
🔗 Using an App Service Environment - aka.ms/azfr/706/03
🔗 Securing web workloads with App Service Environments - aka.ms/azfr/706/04
🔗 Create a free account (Azure) - aka.ms/azfr/706/free
#Microsoft #Azure #AzureFriday

[@ssshyambabu]

This is really useful

[@ralph17p]

The Zone redundancy option in the setup wizard said the minimum number of App Service plans is three, but the pages I've been looking at recently seem to suggest there's a minimum charge of nine when zone redundancy is selected. Has this changed recently, because I had put in an infrastructure design using an ASE, thinking we'd be OK with three, but nine is making it a little rich for my taste - especially as our Devs are having a bit of trouble with deployment to the test environment now that it's isolated and the Web Deploy and FTP endpoints are no longer exposed. I'm new to this and it's a steep learning curve... additional cost and complication makes me think it's still more for the big boys and I should stick with multi-tenant ASPs. Also - "deployment will take a little while". That's an understatement! Our test environment took 18 hours to deploy, which had me thinking something had gone wrong. It got there in the end, but the dev environment on multitenant ASP only took a few minutes, so my expectations were that it might take an hour or so.

[@cyberv]

ASE solution will cost more than other azure app service deployments. However, if considering all the benefits it provides, you should come up with the idea it is worth it or not.

[@czahrobsky]

@@cyberv It sounds like they're making significant advances in both the provisioning time and the pricing model, so the benefits of ASE v3 platform as a service with less management overhead may outweigh the argument for cost savings. If it's your own dedicated hardware, you should have more control over resources in your DEV environment.

[@juanmarti4671]

Uuufff this was informative

[@sau002]

Very nice video. ASE might be exactly what I was looking for. Some more information on pricing on V3 could be helpful

[@timkatsapas]

Putting the cost aside, how different is the storage under the cover when we compare a P3v3 ASP vs an ASEv3? If we running multiple workloads we are seeing a limit to the underlying storage acutally, I assume that the ASEv3 can handle higher iOPS etc yeah? Any clarification on this?