Loading...

Azure Peering Service for Dataverse

Azure Peering Service for Dataverse
Azure Peering Service for Dataverse joao.neto Wed, 04/03/2024 - 14:43
Body

Azure Peering Service for Dataverse:

Introduction

Requirements for Enterprise cloud services access are constantly evolving in terms of number of connections/users, data payload, multi-region/multi-continent access, ....

To overcome this different types of Enterprise architectures are often used : Geo-Partitioned/Hybrid-Cloud/Global load balancing/CDN architectures.

Nonetheless one question remains, how to enhance and improve network performance between Enterprise office locations and Microsoft cloud services?

Azure Peering Service for Dataverse

Microsoft says that MAPS, Microsoft Azure Peering Service, is one of the answers.

What is

A straightforward and easy way to establish direct peering with Microsoft

MAPS is a service that enhances the connectivity to Microsoft cloud services such as Microsoft 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet.

It uses a partnership between ISP's, IXP's and SDCI providers worldwide to provide optimal routing and high-performing connectivity between Enterprise office locations and Microsoft cloud services.

Azure Peering Service for Dataverse

How it works

Microsoft 365, Dynamics 365, and any other Microsoft SaaS services are hosted in multiple Microsoft datacenters and can be accessed from any geographic location.

The Microsoft global network has Microsoft Edge point-of-presence (PoP) locations around the world where it can connect to an end user via their service providers.

Azure Peering Service for Dataverse

Microsoft and partner service providers ensure that the traffic for the prefixes registered with a Peering Service connection enters and exits the nearest Microsoft Edge PoP locations on the Microsoft global network.

Microsoft ensures that the networking traffic egressing from the prefixes registered with Peering Service connections takes the nearest Microsoft Edge PoP locations on the Microsoft global network (Cold-Potato routing).

Why use it

  • If Microsoft services performance are business critical to an Enterprise

  • To provide the shortest path (optimal routing) to Microsoft SaaS products, including Dynamics 365, Microsoft 365, Azure and all Microsoft services accessible from the public Internet

  • Avoid the enormous hops between Enterprise office locations and Microsoft

  • Geo-Redundancy: Microsoft’s interconnected service providers across multiple metro locations allow traffic to reroute via alternate sites if an Edge node experiences performance degradation

  • Monitoring Platform: Service monitoring analyzes user traffic and routing using Microsoft Telemetry

  • Redundancy: With primary and secondary connections, redundancy ensures reliability

  • Route Analytics: Events related to BGP route anomalies (leak or hijack detection) and suboptimal routing are tracked

  • Often in the Peering service partners offer but not in the Microsoft Peering service:

    • Integrated distributed denial-of-service (DDos) protection

    • Traffic isolated from the public Internet

    • SLA's to ensure service availability

How to use it

In what concerns the technical management of the Peering services Microsoft has services available on the following 3 platforms:

  • Azure Portal
  • Azure PowerShell
  • Azure CLI

Before getting started let's state the Requirements for creating a new Peering service connection using the Azure Portal:

  • An Azure account with an active subscription

  • A connectivity provider from the Peering Service partners
    • The Peering provider partner should be the closest to each office location

    • A complete list of the Peering Service partners can be found here in this link

Azure Peering Service for Dataverse
  1. In the Azure portal search box select Peering Services in the search results and then create

  2. On the Basics of Create a peering service connection, enter or select the following information:
    • Azure Peering Service for Dataverse

  3. Next, let's configure the Service connection:
    1. Will need to provide the country, State/Province the Provider (from the available Peering service partners)
    2. Select the provider primary peering location the and ideally the closest one to the target Office network location to enhance
    3. Select the provider backup peering location as the next closest to your network location. A peering service will be active via the backup peering location only in the event of failure of primary peering service location for disaster recovery. If None is selected, internet is the default failover route in the event of primary peering service location failure
    4. Under the Prefixes section, select Create new prefix. In Name, enter a name for the prefix resource. Enter the prefixes that are associated with the service provider in Prefix. In Prefix key, enter the prefix key that was given to you by your provider (ISP or IXP). This key allows Microsoft to validate the prefix and provider who have allocated your IP prefix. If your provider is a Route Server partner, you can create all of your prefixes with the same Peering Service prefix key
      • Azure Peering Service for Dataverse
    5. Select Review + Create and after creating a Peering Service connection, additional validation is performed on the included prefixes. You can review the validation status under the Prefixes section of your Peering Service

Note: For multi-region Enterprise scenarios a unique Peering service connection should be created per office region

Conclusion

another piece of the puzzle

With this offer Microsoft releases another piece of the puzzle regarding network latency performance optimization over cloud services (SaaS), however Peering services isn't the so wished silver bullet while architecturing new PowerApps/Dataverse solutions for complex multi-region Enterprise scenarios, and here's why:

  • Peering services aren't accountable for establishing a private secure network to Microsoft services, though it uses the public infrastructure to route Microsoft services traffic
  • Geographic Power Apps environment distribution will still affect network performance for end-users accessing Apps hover a far distant office location, despite of the overall network performance optimization
  • Regarding custom Power Apps solutions and Apps, Peering services won't improve design patterns with performance and calculation problems
  • Azure Peering Services aren't available as trial

As a final word MAPS is a crucial service for Enterprises having business critical services over Microsoft with a multi-region office distribution and looking for network performance improvement and in solution architectural design.

Azure Peering Service for Dataverse

Image
/sites/default/files/2024-03/MAPS_logo.png

Published on:

Learn more
Featured Articles | Dynamics Chronicles
Featured Articles | Dynamics Chronicles

Welcome to our blog, the content is entirely dedicated to Microsoft Dynamics 365, CRM, Power Platform, Common Data Service (CDS) but also Azure. Follow us !

Share post:

Related posts

General Availability of SQL FCI and AG Features SQL Server Enabled by Azure Arc

We have good news. Two business continuity features for SQL Server enabled by Azure Arc are now generally available: View Failover Cluster In...

22 hours ago

Azure VMware Solution using a public IP down to the NSX-T Edge; configure SNAT, No-SNAT & DNAT

Azure VMware Solution How To Series: Configuring NSX-T SNAT, No-SNAT & DNAT rules   Overview Requirements Lab Environment NAT Rules K...

1 day ago

App attach for Azure Virtual Desktop now generally available

App attach for Azure Virtual Desktop allows IT admins to dynamically attach applications from an application package to a user session in Azur...

2 days ago

A Closer Look at Azure WAF’s Data Masking Capabilities for Azure Front Door

The Azure Web Application Firewall (WAF) on Azure Front Door offers centralized protection for your web applications against vulnerabilities a...

2 days ago

Azure Virtual Network Manager (AVNM) Mesh and Direct Connectivity are Generally Available!

Azure Virtual Network Manager's (AVNM) mesh connectivity configuration and direct connectivity option in the hub and spoke connectivity config...

2 days ago

Azure pricing: How to calculate costs of Azure products and services

In our previous blogs we explained the Azure pricing structure and how customers can estimate their project costs when migrating to Azure or b...

2 days ago

Azure Pricing: How to estimate Azure project costs

In the previous blog we explained how you can learn about Azure pricing with free services and a pay-as-you-go model. Next, lets understand ho...

2 days ago

Azure Pricing: How to navigate Azure pricing options and resources

In this blog we discussed customer pricing needs and how they match different phases of the cloud journey, and we provided various tools and r...

2 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy