Skip to content

Commit 5e196df

Browse files
committed
Fix typos in Communications Gateway connectivity article
1 parent c2b6e7e commit 5e196df

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/communications-gateway/connectivity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 11/20/2023
1212

1313
# Connectivity for Azure Communications Gateway
1414

15-
Each Azure region in your deployment connects to your core network. You need to choose the type of connection (for example, MAPS Voice or Express Route) and route traffic between your network and Azure Communications Gateway with specific IP addresses and domain names.
15+
Each Azure region in your deployment connects to your core network. You must choose the type of connection (for example, Microsoft Azure Peering Service Voice). You must use specific IP addresses and domain names to route traffic between your network and Azure Communications Gateway.
1616

1717
This article describes:
1818

@@ -26,7 +26,7 @@ Azure Communications Gateway supports multiple types of connection to your netwo
2626
- We strongly recommend using Microsoft Azure Peering Service Voice (also called MAPS Voice or MAPSV).
2727
- If you can't use MAPS Voice, we recommend ExpressRoute Microsoft Peering.
2828

29-
The following table lists all the available connection types and whether they're supported for each communications service. The connection types are in the order that we recommend (with recommended services first).
29+
The following table lists all the available connection types and whether they're supported for each communications service. The connection types are in the order that we recommend (with recommended types first).
3030

3131
|Connection type | Operator Connect / Teams Phone Mobile | Microsoft Teams Direct Routing | Zoom Phone Cloud Peering | Notes |
3232
|---------|---------|---------|---------|---------|
@@ -83,7 +83,7 @@ Azure Communications Gateway provides multiple FQDNs:
8383

8484
You must decide whether you want these FQDNs to be `*.commsgw.azure.com` domain names or subdomains of a domain you already own, using [domain delegation with Azure DNS](../dns/dns-domain-delegation.md).
8585

86-
Domain delegation provides topology hiding and might increase customer trust, but requires giving us full control over the subdomain that you delegate. For Microsoft Teams Direct Routing, choose domain delegation if you don't want customers to see an `*.commsgw.azure.com` in their Microsoft 365 admin centers.
86+
Domain delegation provides topology hiding and might increase customer trust, but requires giving us full control over the subdomain that you delegate. For Microsoft Teams Direct Routing, choose domain delegation if you don't want customers to see a `*.commsgw.azure.com` address in their Microsoft 365 admin centers.
8787

8888
## Related content
8989

0 commit comments

Comments
 (0)