Skip to content

Commit da723b1

Browse files
authored
Update 6-configure-peering-for-expressroute-deployment.md
1 parent d4e9279 commit da723b1

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

learn-pr/wwl-azure/design-implement-azure-expressroute/includes/6-configure-peering-for-expressroute-deployment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@ This comparison table compares Private peering with Microsoft peering.
1818

1919
| Feature | ExpressRoute Private Peering | ExpressRoute Microsoft Peering |
2020
|-----------------------------|-----------------------------------------------|-----------------------------------------------|
21-
| **Purpose** | Connects directly to Azure virtual networks | Connects to Microsoft services like Office 365, Dynamics 365, and Azure PaaS services |
21+
| **Purpose** | Connects directly to Azure virtual networks | Connects to Microsoft services like Microsoft 365, Dynamics 365, and Azure PaaS services |
2222
| **Traffic Type** | Private IP traffic | Public IP traffic |
2323
| **Access** | Direct access to Azure VMs and services within virtual networks | Access to Microsoft SaaS services and Azure PaaS services |
2424
| **Security** | Traffic stays on private network, not exposed to the internet | Traffic is routed over public IPs but through a private connection |
25-
| **Use Cases** | Enterprise applications, databases, and other workloads requiring secure, high-performance connectivity | Access to Microsoft services like Office 365, Dynamics 365, and Azure PaaS services |
25+
| **Use Cases** | Enterprise applications, databases, and other workloads requiring secure, high-performance connectivity | Access to Microsoft services like Microsoft 365, Dynamics 365, and Azure PaaS services |
2626
| **Network Isolation** | Provides network isolation from the public internet | Doesn't provide network isolation from the public internet, but ensures traffic doesn't traverse the public internet |
2727
| **Bandwidth Options** | Offers scalable bandwidth options | Offers scalable bandwidth options |
2828

@@ -43,4 +43,4 @@ ExpressRoute locations, also known as peering locations or meet-me locations, ar
4343

4444
- **Compliance and regulatory requirements**: If your organization has specific compliance or regulatory requirements, ensure that the peering location meets these standards. Compliance requirements might include data residency or industry-specific regulations.
4545

46-
- **Future growth and scalability**: Consider your future growth plans and ensure that the peering location can accommodate increased bandwidth and other connections as your needs evolve.
46+
- **Future growth and scalability**: Consider your future growth plans and ensure that the peering location can accommodate increased bandwidth and other connections as your needs evolve.

0 commit comments

Comments
 (0)