Skip to content

Commit e9a2828

Browse files
committed
Update connectivity article for lab deployments
1 parent ebb45e8 commit e9a2828

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

articles/communications-gateway/connectivity.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: rcdun
55
ms.author: rdunstan
66
ms.service: communications-gateway
77
ms.topic: concept-article
8-
ms.date: 11/20/2023
8+
ms.date: 01/08/2024
99

1010
#CustomerIntent: As someone planning a deployment, I want to learn about my options for connectivity, so that I can start deploying
1111
---
@@ -32,12 +32,17 @@ The following table lists all the available connection types and whether they're
3232
|---------|---------|---------|---------|---------|
3333
| MAPS Voice ||||- Best media quality because of prioritization with Microsoft network<br>- No extra costs<br>- See [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md)|
3434
|ExpressRoute Microsoft Peering ||||- Easy to deploy<br>- Extra cost<br>- Consult with your onboarding team and ensure that it's available in your region<br>- See [Using ExpressRoute for Microsoft PSTN services](/azure/expressroute/using-expressroute-for-microsoft-pstn)|
35-
|Public internet ||||- No extra setup<br>- Not recommended for production|
35+
|Public internet |⚠️ Lab deployments only|||- No extra setup<br>- Where available, not recommended for production |
3636

37-
Set up your network as in the following diagram and configure it in accordance with any network connectivity specifications for your chosen communications services. Your network must have two sites with cross-connect functionality. For more information on the reliability design for Azure Communications Gateway, see [Reliability in Azure Communications Gateway](reliability-communications-gateway.md).
37+
> [!NOTE]
38+
> The Operator Connect and Teams Phone Mobile programs do not allow production deployments to use the public internet.
39+
40+
Set up your network as in the following diagram and configure it in accordance with any network connectivity specifications for your chosen communications services. For production deployments, your network must have two sites with cross-connect functionality. For more information on the reliability design for Azure Communications Gateway, see [Reliability in Azure Communications Gateway](reliability-communications-gateway.md).
3841

3942
:::image type="content" source="media/azure-communications-gateway-network.svg" alt-text="Network diagram showing Azure Communications Gateway deployed into two Azure regions within one Azure Geography. The Azure Communications Gateway resource in each region connects to a communications service and both operator sites. Azure Communications Gateway uses MAPS or Express Route as its peering service between Azure and an operators network." lightbox="media/azure-communications-gateway-network.svg":::
4043

44+
Lab deployments have one Azure service region and must connect to one site in your network.
45+
4146
## IP addresses and domain names
4247

4348
Azure Communications Gateway (ACG) deployments require multiple IP addresses and fully qualified domain names (FQDNs). The following diagram and table describe the IP addresses and FQDNs that you might need to know about.

0 commit comments

Comments
 (0)