You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/design-implement-azure-expressroute/includes/6-configure-peering-for-expressroute-deployment.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,11 @@ This comparison table compares Private peering with Microsoft peering.
|**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 |
22
22
|**Traffic Type**| Private IP traffic | Public IP traffic |
23
23
|**Access**| Direct access to Azure VMs and services within virtual networks | Access to Microsoft SaaS services and Azure PaaS services |
24
24
|**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 |
26
26
|**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 |
@@ -43,4 +43,4 @@ ExpressRoute locations, also known as peering locations or meet-me locations, ar
43
43
44
44
-**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.
45
45
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