Skip to content

Commit cd821fa

Browse files
committed
Removing a merge conflict typo
1 parent 08e1645 commit cd821fa

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

articles/frontdoor/front-door-backend-pool.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ ms.author: sharadag
1717
This article describes concepts about how to map your app deployment with Azure Front Door. It also explains the different terms in Front Door configuration around app backends.
1818

1919
## Backends
20-
<<<<<<< HEAD
2120
A backend is equal to an app's deployment instance in a region. Front Door supports both Azure and non-Azure backends, so the region isn't only restricted to Azure regions. Also, it can be your on-premises datacenter or an app instance in another cloud.
2221

2322
Front Door backends refer to the host name or public IP of your app, which can serve client requests. Backends shouldn't be confused with your database tier, storage tier, and so on. Backends should be viewed as the public endpoint of your app backend. When you add a backend in a Front Door backend pool, you must also add the following:

0 commit comments

Comments
 (0)