Updates

Author: johndowns

articles/frontdoor/manager.md

@@ -6,7 +6,7 @@ author: duongau
 ms.service: frontdoor
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 03/16/2022
+ms.date: 06/13/2022
 ms.author: duau
 ---
 
@@ -18,25 +18,14 @@ The Front Door manager in Azure Front Door Standard and Premium provides an over
 
 ## Routes within an endpoint
 
-An endpoint is a logical grouping of one or more routes that associates with domains. A route contains the origin group configuration and routing rules between domains and origins. An endpoint can have one or more routes. A route can have multiple domains but only one origin group. You need to have at least one configured route in order for traffic to route between your domains and the origin group.
+An [*endpoint*](endpoint.md) is a logical grouping of one or more routes that are associated with domain names. A route contains the origin group configuration and routing rules between domains and origins. An endpoint can have one or more routes. A route can have multiple domains but only one origin group. You need to have at least one configured route in order for traffic to route between your domains and the origin group.
 
 > [!NOTE]
 > * You can *enable* or *disable* an endpoint or a route. 
 > * Traffic will only flow to origins once both the endpoint and route is **enabled**.
 >
 
-Domains configured within a route can either be a custom domain or an endpoint domain. For more information about custom domains, see [create a custom domain](standard-premium/how-to-add-custom-domain.md) with Azure Front Door. Endpoint domains refer to the auto generated domain name when you create a new endpoint. The name is a unique endpoint hostname with a hash value in the format of `endpointname-hash.z01.azurefd.net`. The endpoint domain will be accessible if you associate it with a route. 
-
-### Reuse of an endpoint domain name
-
-An endpoint domain can be reused within the same tenant, subscription, or resource group scope level. You can also choose to not allow the reuse of an endpoint domain. The Azure portal default settings allow tenant level reuse of the endpoint domain. You can use command line to configure the scope level of the endpoint domain reuse. The Azure portal will use the scope level you define through the command line once it has been changed.
-
-| Value | Behavior |
-|--|--|
-| TenantReuse | This is the default value. Object with the same name in the same tenant will receive the same domain label. |
-| SubscriptionReuse | Object with the same name in the same subscription will receive the same domain label. |
-| ResourceGroupReuse | Object with the same name in the same resource group will receive the same domain label. |
-| NoReuse | Object with the same will receive a new domain label for each new instance. |
+Domains configured within a route can either be a custom domain or an endpoint domain. For more information about custom domains, see [create a custom domain](standard-premium/how-to-add-custom-domain.md) with Azure Front Door. Endpoint domains refer to the auto generated domain name when you create a new endpoint. The name is a unique endpoint hostname with a hash value in the format of `endpointname-hash.z01.azurefd.net`. The endpoint domain will be accessible if you associate it with a route.
 
 ## Security policy in an endpoint
 
@@ -55,6 +44,7 @@ In Azure Front Door (classic), the Front Door manager is called Front Door desig
 
 ## Next steps
 
+* Learn about [endpoints](endpoint.md).
 * Learn how to [configure endpoints with Front Door manager](how-to-configure-endpoints.md).
 * Learn about the Azure Front Door [routing architecture](front-door-routing-architecture.md).
 * Learn [how traffic is matched to a route](front-door-routing-architecture.md) in Azure Front Door.