DNS and alert updates

Author: ccompy

articles/app-service/environment/using-an-ase.md

@@ -5,7 +5,7 @@ author: ccompy
 
 ms.assetid: a22450c4-9b8b-41d4-9568-c4646f4cf66b
 ms.topic: article
-ms.date: 01/01/2020
+ms.date: 3/26/2020
 ms.author: ccompy
 ms.custom: seodec18
 ---
@@ -115,6 +115,22 @@ For information about how to create an ILB ASE, see [Create and use an ILB ASE][
 
 The SCM URL is used to access the Kudu console or for publishing your app by using Web Deploy. For information on the Kudu console, see [Kudu console for Azure App Service][Kudu]. The Kudu console gives you a web UI for debugging, uploading files, editing files, and much more.
 
+### DNS configuration 
+
+When you use an External ASE, apps made in your ASE are registered with Azure DNS. With an ILB ASE, you must manage your own DNS. 
+
+To configure DNS with your ILB ASE:
+
+    create a zone for &ltASE name&gt.appserviceenvironment.net
+    create an A record in that zone that points * to the ILB IP address
+    create an A record in that zone that points @ to the ILB IP address
+    create a zone in &ltASE name&gt.appserviceenvironment.net named scm
+    create an A record in the scm zone that points * to the ILB IP address
+
+The DNS settings for your the ASE default domain do not restrict your apps to only being accessible by those names. You can set a custom domain name without any validation on your apps in an ILB ASE. If you then want to create a zone named *contoso.net*, you could do so and point it to the ILB IP address. The custom domain name works for app requests but doesn't for the scm site. The scm site is only available at *&ltASE name&gt.appserviceenvironment.net*. 
+
+The zone named <ASE name>.appserviceenvironment.net is globally unique. Before May 2019, customers were able to specify the domain suffix of the ILB ASE. If you wanted to use *.contoso.com* for the domain suffix you were able do so and that would include the scm site. There were challenges with that model including; managing the default SSL certificate, lack of single sign on with the scm site, and the requirement to use a wildcard certificate. The ILB ASE default certificate upgrade process was also very disruptive and caused application restarts. To solve these problems, the ILB ASE behavior was changed to use a domain suffix based on the name of the ASE and with a Microsoft owned suffix. The change to the ILB ASE behavior only affects ILB ASEs made after May 2019. Pre-existing ILB ASEs must still manage the default certificate of the ASE and their DNS configuration.
+
 ## Publishing
 
 In an ASE, as with the multitenant App Service, you can publish by these methods:
@@ -164,7 +180,18 @@ To enable logging on your ASE:
 
 ![ASE diagnostic log settings][4]
 
-If you integrate with Log Analytics, you can see the logs by selecting **Logs** from the ASE portal and creating a query against **AppServiceEnvironmentPlatformLogs**.
+If you integrate with Log Analytics, you can see the logs by selecting **Logs** from the ASE portal and creating a query against **AppServiceEnvironmentPlatformLogs**. Logs are only emitted when your ASE has an event that will trigger it. If your ASE does not have such an event, there will not be any logs. To quickly see an example of logs in your Log Analytics workspace, perform a scale operation with one of the App Service plans in your ASE. You can then run a query against **AppServiceEnvironmentPlatformLogs** to see those logs. 
+
+**Creating an alert**
+
+To create an alert against your logs, follow the instructions in [Create, view and manage log alerts using Azure Monitor][logalerts]. In brief:
+
+* Open the Alerts page in your ASE portal
+* Select **New alert rule**
+* Select your Resource to be your Log Analytics workspace
+* Set your condition with a custom log search to use a query like, "AppServiceEnvironmentPlatformLogs | where ResultDescription contains "has begun scaling" or whatever you want. Set the threshhold as appropriate. 
+* Add or create an action group as desired. The action group is where you define the response to the alert such as sending an email or an SMS message
+* Name your alert and save it.
 
 ## Upgrade preference
 
@@ -240,3 +267,4 @@ To delete an ASE:
 [AppDeploy]: ../deploy-local-git.md
 [ASEWAF]: app-service-app-service-environment-web-application-firewall.md
 [AppGW]: ../../application-gateway/application-gateway-web-application-firewall-overview.md
+[logalerts]: ../../azure-monitor/platform/alerts-log.md