Merge pull request #301550 from gabesmsft/main

Update rule-based-routing-custom-domain.md

Author: JamesJBarnett

articles/container-apps/rule-based-routing-custom-domain.md

@@ -21,14 +21,53 @@ HTTP route configurations support custom domains, allowing you to route traffic
 - SSL certificate for your domain (unless using automatic certificates)
 - Container apps deployed to your environment
 
+## Custom domain configuration
+
+Using the DNS provider hosting your domain, create the appropriate DNS records for your custom domain.
+- If you are using the root domain (for example, `contoso.com`), create the following DNS records:
+
+	| Record type | Host | Value |
+	|--|--|--|
+	| A | `@` | The IP address of your Container Apps environment. |
+	| TXT | `asuid` | The domain verification code. |
+	
+- If you are using a subdomain (for example, `www.contoso.com`), create the following DNS records:
+
+	| Record type | Host | Value |
+	|--|--|--|
+	| A | The subdomain (for example, `www`) | The IP address of your Container Apps environment. |
+	| TXT | `asuid.{subdomain}` (for example, `asuid.www`) | The domain verification code. |
+
+> [!NOTE]
+> The IP address of your Container Apps environment and the domain verification code can be found in the [Custom DNS suffix settings](./environment-custom-dns-suffix.md#add-a-custom-dns-suffix-and-certificate) of your Container Apps environment.
+>
+> Don't bind the custom domain to your Container Apps environment or to a container app.  Domains are only bound to one app, route, or environment.
+
+## Route configuration
+
+Update your Container Apps YAML file to include a `customDomains` section. Include a `bindingType` and `certificateId`, based on the following criteria:
+
+| bindingType value | Description | 
+|--|--|
+| Disabled | No certificate is provided. The domain is only available over HTTP, and HTTPS is not available. |
+| Auto | A certificate is optional. If a managed certificate is already created for this domain, it is added to the route automatically. Otherwise, the domain is initially only available over HTTP. To create a managed certificate for this domain, create a new managed certificate after the route is created. After the certificate is created, it is automatically added to the route. |
+| SniEnabled | A certificate is required. |
+
+| Certificate type | certificateId format |
+| -- | -- |
+| None | Leave blank |
+| Managed | `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/managedEnvironments/{ContainerAppEnvironmentName}/managedCertificates/{CertificateFriendlyName}` |
+| Unmanaged | `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/managedEnvironments/{ContainerAppEnvironmentName}/certificates/{CertificateFriendlyName}` |
+
 > [!NOTE]
-> To set up your own custom domain and certificate, see [Custom domain names and free managed certificates](./custom-domains-managed-certificates.md).
+> To add a certificate to your environment, use one of the following methods:
+> - To add a Container Apps managed certificate, use the [az containerapp env certificate create](/cli/azure/containerapp/env/certificate#az-containerapp-env-certificate-create) CLI command.
+> - To bring your own existing certificate, use the [az containerapp env certificate upload](/cli/azure/containerapp/env/certificate#az-containerapp-env-certificate-upload) CLI command.
 >
-> If you set `bindingType: "Auto"`, you don't need a `certificateId`. Create the route first so the certificate registration check for ownership succeeds. Once you set up the certificate, Container Apps automatically adds it to the route spec and binds it to the domain. The site is only accessible over HTTP (not HTTPS) until setup is complete.
+> Don't bind the certificate to a container app.
 
-## Configuration
 
-Update your Container Apps YAML file to include a `customDomains` section. The following example demonstrates how to set up this configuration.
+The following example demonstrates how to set up the route configuration.
 
 ```yml
 customDomains:
@@ -80,22 +119,12 @@ Other properties not listed that may affect your routes include the following.
 | `target.label` | Route to a specific labeled revision within a container app. |
 | `target.revision` | Route to a specific revision within a container app. |
 
-## Work with your custom domain
+## Work with your route configuration
 
-Use the following commands to configure and use your custom domain mapping.
+Use the following commands to manage your route configuration.
 
 Before running the following commands, make sure to replace placeholders surrounded by `<>` with your own values.
 
-### List route configurations
-
-Use `az containerapp env http-route-config list` to list all the defined route configurations.
-
-```azurecli
-az containerapp env http-route-config list \
-    --resource-group <RESOURCE_GROUP_NAME> \
-    --name <ENVIRONMENT_NAME>
-```
-
 ### Create a new route configuration
 
 Use `az containerapp env http-route-config create` to create a new route configuration.
@@ -108,6 +137,16 @@ az containerapp env http-route-config create \
     --yaml <CONTAINER_APPS_CONFIG_FILE>
 ```
 
+### List route configurations
+
+Use `az containerapp env http-route-config list` to list all the defined route configurations.
+
+```azurecli
+az containerapp env http-route-config list \
+    --resource-group <RESOURCE_GROUP_NAME> \
+    --name <ENVIRONMENT_NAME>
+```
+
 ### Update a route configuration
 
 Use `az containerapp env http-route-config update` to update an existing route configuration.