Merge branch 'jsaraco/addMapsPartnerOverview' of https://github.com/JonathanSaraco/azure-docs-pr into ip-ps-overview

Author: halkazwini

articles/internet-peering/maps-partner-overview.md

@@ -0,0 +1,45 @@
+---
+title: Azure Peering Service partner overview
+description: Learn about MAPS and how to become a partner.
+services: internet-peering
+author: jsaraco
+ms.service: internet-peering
+ms.topic: conceptual
+ms.date: 04/07/2023
+ms.author: jsaraco
+ms.custom: template-overview, engagement-fy23
+---
+
+# Azure Peering Service partner overview
+
+## Background
+
+For an overview of the Azure Peering Service product, see [MAPS Overview](../peering-service/about.md)
+
+## MAPS partner requirements
+
+To become a MAPS partner, the following technical requirements must be followed [MAPS partner requirements](./walkthrough-peering-service-all.md#technical-requirements)
+
+If you can follow all of the requirements listed and would like to become a MAPS partner, an agreement must be signed. Contact [email protected] to get started.
+
+## Types of MAPS connections
+
+To become a MAPS partner, you must request a direct peering interconnect with Microsoft. They come in three types depending on your use case.
+
+- **AS8075** - A direct peering interconnect enabled for MAPS made for Internet Service providers (ISPs)
+- **AS8075 (with Voice)** - A direct peering interconnect enabled for MAPS made for Internet Service providers (ISPs). This type is optimized for communications services (messaging, conferencing, etc.), and allows you to integrate your communications services infrastructure (SBC, SIP gateways, and other infrastructure device) with Azure Communication Services and Microsoft Teams.
+- **AS8075 (with exchange route server)** - A direct peering interconnect enabled for MAPS and made for Internet Exchange providers (IXPs) who require a route server.
+
+### Monitoring platform
+
+Service monitoring is offered to analyze user traffic and routing. Metrics are available in the Azure portal to track the performance and availability of your MAPS peering, and they are described here: [MAPS Monitoring Platform](../peering-service/about.md#monitoring-platform)
+
+In addition, MAPS partners are able to see received routes reported in the Azure portal.
+
+:::image type="content" source="./media/maps-partner-overview/maps-partner-latency-report.png" alt-text="Diagram showing monitoring platform for MAPS.":::
+
+## Next steps
+
+- To establish a Direct interconnect for MAPS, see [Internet peering for MAPS walkthrough](./walkthrough-peering-service-all.md)
+- To establish a Direct interconnect for MAPS Communications Services, see [Internet peering for MAPS Communications Services walkthrough](./walkthrough-communications-services-partner.md)
+- To establish a Direct interconnect for MAPS Exchange with Route Server, see [Internet peering for MAPS Exchange with Route Server walkthrough](./walkthrough-exchange-route-server-partner.md)

articles/internet-peering/media/maps-partner-overview/maps-partner-latency-report.png

@@ -12,6 +12,8 @@
     href: policy.md
   - name: Prerequisites to set up peering with Microsoft
     href: prerequisites.md
+  - name: Azure Peering Service partner overview
+    href: maps-partner-overview.md
   - name: Peering registered prefix requirements
     href: peering-registered-prefix-requirements.md
   - name: Internet peering FAQ

articles/internet-peering/toc.yml

@@ -39,6 +39,8 @@ To establish direct interconnect for Peering Service, follow these requirements:
 
 ## Establish Direct Interconnect for Peering Service
 
+Refer to the [Azure Peering Service partner overview requirements](./maps-partner-overview.md#maps-partner-requirements) and ensure that you sign a Microsoft Azure Peering Service agreement before proceeding.
+
 To establish a Peering Service interconnect with Microsoft, follow the following steps:
 
 ### 1. Associate your public ASN with your Azure subscription