Collection of Front Door origins that share health probe and load-balancing settings (latency, priority and weight). Choosing an origin by path is never done at this level.
Also called Backend pool (Front Door classic).
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Origin group in context, with comparison tables and the common traps.
Terms in this definition
- Share
In OpenSharing, the container you fill with tables, views, volumes, models and notebooks for recipients. You need
CREATE SHAREon the metastore to make one; add a schema and all its assets, including later ones, go with history. - Health probe
A TCP, HTTP or HTTPS check a load balancer uses to decide whether backends are healthy. For an HTTP probe, its path has to return HTTP 200.
- Priority
Routing method in Traffic Manager for active/passive failover: traffic goes to whichever healthy endpoint has the highest priority.
- Origin
Host behind Front Door that serves the content, such as an App Service app, storage, a load balancer or any custom host given by FQDN. An App Service app counts as one origin regardless of its worker count.
- PATH
Parent-child hierarchies in DAX rely on this function. For each row it builds one delimited text value listing the IDs of the row's ancestors, top level first and ending with the row's own ID, which PATHITEM, PATHLENGTH and friends can then pick apart.
Related terms
- Latency sensitivity
Setting on a Front Door origin group, in milliseconds and 0 by default, that extends the range around the quickest origin; every origin within that range receives traffic according to its weight.
- Route (Front Door)
In Azure Front Door Standard and Premium, ties a set of domains, protocols and path patterns to one origin group. When matching, an exact path beats any wildcard, and longer wildcards beat shorter ones.
- Rule set (Front Door)
Rules in Azure Front Door Standard or Premium that run once a route has matched; they can change requests and responses or send traffic to a different origin group.