Merge pull request #189779 from MicrosoftDocs/release-preview-azure-publicmec-withoperator

Release preview azure publicmec withoperator-- scheduled Publish at 3:30PM of 2/27

Author: huypub

articles/public-multi-access-edge-compute-mec/considerations-for-deployment.md

@@ -0,0 +1,89 @@
+---
+title: Considerations for deployment in Azure public MEC Preview
+description: Learn about considerations for customers to plan for before they deploy applications in an Azure public multi-access edge compute (MEC) solution.
+author: m0nikama
+ms.author: monikama
+ms.service: public-multi-access-edge-compute-mec
+ms.topic: conceptual
+ms.date: 02/24/2022
+ms.custom: template-concept
+---
+
+# Considerations for deployment in Azure public MEC Preview
+
+Azure public multi-access edge compute (MEC) Preview sites are small-footprint extensions of Azure. They're placed in or near mobile operators' data centers in metro areas, and are designed to run workloads that require low latency while being attached to the mobile network. This article focuses on the considerations that customers should plan for before they deploy applications in the Azure public MEC.
+
+## Prerequisites
+
+- If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+
+- Add an allowlisted subscription to your Azure account, which allows you to deploy resources in Azure public MEC. If you don't have an active allowed subscription, contact the [Azure public MEC product team](https://aka.ms/azurepublicmec).
+
+## Best practices
+
+For Azure public MEC, follow these best practices:
+
+- Deploy in Azure public MEC only those components of the application that are latency sensitive or need low latency compute at the Azure public MEC. Deploy in the parent region those components of the application that perform control plane and management plane functionalities.
+
+- Because Azure public MEC sites are connected to the Telco network, accessing resources deployed in it over the internet isn't allowed. To access VMs deployed in the Azure public MEC, deploy jump box virtual machines (VMs) or Azure Bastion in a virtual network (VNet) in the parent region.
+
+- For compute resources in the Azure public MEC, deploy Azure Key Vault in the Azure region to provide secrets management and key management services.
+
+- Use VNet peering between the VNets in the Azure public MEC and the VNets in the parent region. IaaS resources can communicate privately through the Microsoft network and don't need to access the public internet.
+
+## Azure public MEC architecture
+
+Deploy application components that require low latencies in the Azure public MEC, and components that are non-latency sensitive in the Azure region.
+
+### Azure region
+
+The Azure region should run the components of the application that perform control and management plane functions and aren't latency sensitive.
+
+The following sections show some examples.
+
+#### Azure database and storage
+
+- Azure databases: Azure SQL, Azure Database for MySQL, and so on
+- Storage accounts
+- Azure Blob Storage
+
+#### AI and Analytics
+
+- Azure Machine Learning Services
+- Azure Analytics Services
+- Power BI
+- Azure Stream Analytics
+
+#### Identity services
+
+- Azure Active Directory
+
+#### Secrets management
+
+- Azure Key Vault
+
+### Azure public MEC
+
+Azure public MEC should run components that are latency sensitive and need faster response times from compute resources. To do so, run your application on compute services such as Azure Virtual Machines and Azure Kubernetes Service in the public MEC.
+
+## Availability and resiliency
+
+Applications you deploy in the Azure public MEC can be made available and resilient by using the following methods:
+
+- Deploy resources in active/standby, with primary resources in the Azure public MEC and standby resources in the parent Azure region. If there's a failure in the Azure public MEC, the resources in the parent region become active.
+
+- Use the [Azure backup and disaster recovery solution](/azure/architecture/framework/resiliency/backup-and-recovery), which provides [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) and Azure Backup features. This solution:
+  - Actively replicates VMs from the Azure public MEC to the parent region and makes them available to fail over and fail back if there's an outage.
+  - Backs up VMs to prevent data corruption or lost data.
+
+   > [!NOTE]
+   > The Azure backup and disaster recovery solution for Azure public MEC supports only Azure Virtual Machines.
+
+A trade-off exists between availability and latency. Failing over the application from the Azure public MEC to the Azure region ensures that the application is available, but might increase the latency to the application.
+
+## Next steps
+
+To deploy a virtual machine in Azure public MEC using an Azure Resource Manager (ARM) template, advance to the following article:
+
+> [!div class="nextstepaction"]
+> [Quickstart: Deploy a virtual machine in Azure public MEC using an ARM template](quickstart-create-vm-azure-resource-manager-template.md)

articles/public-multi-access-edge-compute-mec/index.yml

@@ -0,0 +1,53 @@
+### YamlMime:Landing
+
+title: Azure public multi-access-edge compute documentation # < 60 chars
+summary: Learn how to use Azure public multi-access-edge compute (MEC) to develop and deploy latency-sensitive workloads, integrated with Azure compute, at the 5G network edge. # < 160 chars
+
+metadata:
+  title: Azure public multi-access-edge compute documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
+  description: Learn how to use Azure public multi-access-edge compute (MEC) to develop and deploy latency-sensitive workloads, integrated with Azure compute, at the 5G network edge. # Required; article description that is displayed in search results. < 160 chars.
+  ms.service: public-multi-access-edge-compute-mec # Required; service per approved list. service slug assigned to your service by ACOM.
+  ms.topic: landing-page # Required
+  author: reemas-new # Required; your GitHub user alias, with correct capitalization.
+  ms.author: reemas # Required; microsoft alias of author; optional team alias.
+  ms.date: 02/24/2022
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+
+  # Card
+  - title: About Azure public MEC
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: What is Azure public MEC?
+            url: overview.md
+      - linkListType: concept
+        links:
+          - text: Key concepts for Azure public MEC
+            url: key-concepts.md        
+          - text: Considerations for deployment in Azure public MEC
+            url: considerations-for-deployment.md
+
+  # Card
+  - title: Get started
+    linkLists:
+      - linkListType: quickstart
+        links:
+          - text: Create VM using ARM template
+            url: quickstart-create-vm-azure-resource-manager-template.md
+          - text: Create VM using Azure CLI
+            url: quickstart-create-vm-cli.md
+     
+ # Card
+  - title: Tutorials
+    linkLists:
+      - linkListType: tutorial
+        links:
+          - text: Create VM using Go SDK
+            url: tutorial-create-vm-using-go-sdk.md
+          - text: Create VM using Python SDK
+            url: tutorial-create-vm-using-python-sdk.md

articles/public-multi-access-edge-compute-mec/key-concepts.md

@@ -0,0 +1,105 @@
+---
+title: Key concepts for Azure public MEC Preview
+description: Learn about important concepts for Azure public multi-access edge compute (MEC). 
+author: moushumig
+ms.author: moghosal
+ms.service: public-multi-access-edge-compute-mec
+ms.topic: conceptual
+ms.date: 02/24/2022
+ms.custom: template-concept
+---
+
+# Key concepts for Azure public MEC Preview
+
+This document describes important concepts for Azure public multi-access edge compute (MEC) Preview.
+
+## ExtendedLocation field
+
+All resource providers provide an additional field called [extendedLocation](/javascript/api/@azure/arm-compute/extendedlocation), which you use to deploy resources in the Azure public MEC.
+
+## Azure Edge Zone ID
+
+Every Azure public MEC site has an Azure Edge Zone ID. This ID is one of the attributes that the `extendedLocation` field uses to differentiate sites.
+
+## Azure CLI and SDKs
+
+SDKs for services supported in Azure public MEC have been updated. For information about how to use these SDKs for deployment, see [Tutorial: Deploy resources in Azure public MEC using the Go SDK](tutorial-create-vm-using-go-sdk.md), [Tutorial: Deploy a virtual machine in Azure public MEC using Python SDK](tutorial-create-vm-using-python-sdk.md), and [Quickstart: Deploy a virtual machine in Azure public MEC using Azure CLI](quickstart-create-vm-cli.md).
+
+## ARM templates
+
+You can use ARM Templates to deploy resources in the Azure public MEC. Here's an example of how `extendedLocation` is used in an Azure Resource Manager (ARM) template to deploy a virtual machine (VM):
+
+```json
+{
+  ...
+  "type": "Microsoft.Compute/virtualMachines"
+  "extendedLocation": {
+    "type": "EdgeZone",
+    "name": <edgezoneid>,
+    }
+  ...
+}
+```
+
+## Parent regions
+
+Every Azure public MEC site is associated with a parent Azure region. This region hosts all the control plane functions associated with the services running in the Azure public MEC. The following table lists active Azure public MEC sites, along with their Edge Zone ID and associated parent region.
+
+| Telco provider | Azure public MEC name | Edge Zone ID | Parent region |
+| -------------- | --------------------- | ------------ | ------------- |
+| AT&T | ATT Atlanta A | attatlanta1 | East US 2 |
+| AT&T | ATT Dallas A | attdallas1 | South Central US |
+
+## Azure services
+
+### Azure virtual machines
+
+Azure public MEC supports specific compute and GPU VM SKUs. The following table lists the supported VM sizes:
+
+| Type | Series | VM size |
+| ---- | ------ | ------- |
+| VM | D-series | D2s_v3, D4s_v3, D8s_v3 |
+| VM | E-series | E4s_v3, E8s_v3 |
+| GPU | NCasT4_v3-series | Standard_NC4asT4_v3, Standard_NC8asT4_v3 |
+
+### Public IP
+
+Azure public MEC allows users to create public IPs that can be then associated with resources such as Azure Virtual Machines, Azure Standard Load Balancer, and Azure Kubernetes Clusters. All the Azure public MEC IPs are the Standard public IP SKU.
+
+### Azure Bastion
+
+Azure Bastion is a service you deploy that lets you connect to a virtual machine by using your browser and the Azure portal. To access a VM deployed in the Azure public MEC, the Bastion host must be deployed in a VNet in the parent region of the Azure public MEC site.
+
+### Azure Load Balancer
+
+The Azure public MEC supports the Standard Load Balancer SKU.
+
+### Network Security Groups
+
+Network Security Groups should be created in the parent region, and then can be associated to resources created in the Azure public MEC.
+
+### Resource Groups
+
+Resource Groups should  be created in the parent Azure region, and then can be associated to resources created in the Azure public MEC.
+
+### Storage Services
+
+Azure public MEC only supports creating Standard SSD Managed Disks. All other storage services are currently not supported in the public MEC.
+
+### Default outbound access
+
+Because [default outbound access](/azure/virtual-network/ip-services/default-outbound-access) isn't supported on the public MEC, manage your outbound connectivity by using one of the following methods:
+
+- Use the frontend IP addresses of a Load Balancer for outbound via outbound rules.
+- Assign a public IP to the VM.
+
+### DNS Resolution
+
+By default, all services running in the Azure public MEC use the DNS infrastructure in the Azure parent region.
+
+## Next steps
+
+To learn about considerations for deployment in the Azure public MEC, advance to the following article:
+
+> [!div class="nextstepaction"]
+> [Considerations for deployment in the Azure public MEC](considerations-for-deployment.md)

articles/public-multi-access-edge-compute-mec/media/overview/azure-public-mec-benefits.png

@@ -0,0 +1,76 @@
+---
+title: What is Azure public MEC Preview?
+description: Learn about the benefits of Azure public multi-access edge compute (MEC) and how it works.
+author: dahliacanter
+ms.author: dahliac
+ms.service: public-multi-access-edge-compute-mec
+ms.topic: overview
+ms.date: 02/24/2022
+ms.custom: template-overview
+---
+
+# What is Azure public MEC Preview?
+
+Azure public multi-access edge compute (MEC) Preview sites are small-footprint extensions of Azure. They're placed in or near mobile operators' data centers in metro areas, and are designed to run workloads that require low latency while being attached to the mobile network.  Azure public MEC is offered in partnership with the operators. The placement of the infrastructure offers lower latency for applications that are accessed from mobile devices connected to the 5G mobile network.
+
+Azure public MEC provides secure, reliable, high-bandwidth connectivity between applications that run close to the user while being served by the Microsoft global network. Azure public MEC offers a set of Azure services like Azure Virtual Machines, Azure Load Balancer, and Azure Kubernetes for Edge, with the ability to leverage and connect to other Azure services available in the Azure region.
+
+Some of the industries and use cases where Azure public MEC can provide benefits are:
+
+- Media streaming and content delivery
+- Real-time analytics and inferencing via artificial intelligence and machine learning
+- Rendering for mixed reality
+- Connected automobiles
+- Healthcare
+- Immersive gaming experiences
+- Low latency applications for the retail industry
+
+:::image type="content" source="./media/overview/azure-public-mec-benefits.png" alt-text="Diagram showing the benefits of Azure public MEC.":::
+
+## Benefits of Azure public MEC
+
+Azure public MEC has the following benefits:
+
+- Low latency applications at the 5G network edge:
+  
+  - Enterprises and developers can run low-latency applications by using the operator’s public 5G network connectivity. This connectivity is architected with a direct, dedicated, and optimized connection to the operator’s mobility core network.
+
+- Access to key Azure services and experiences:
+  - Azure-managed toolset: Azure customers can provision and manage their Azure public MEC services and workloads through the Azure portal and other essential Azure tools.
+  - Consistent developer experience: Developing and building applications for the public MEC utilizes the same array of features and tools that Azure uses.
+
+- Access to a rich partner ecosystem:
+  - ISVs working on optimized and scalable applications for edge computing can use the Azure public MEC solution for building solutions. These solutions offer low latency and leverage the 5G mobility network and connected scenarios.
+
+## Service offerings for Azure public MEC
+
+Azure public MEC enables some key Azure services for customers to deploy. The control plane for these services remains in the region and the data plane is deployed at the edge, resulting in a smaller Azure footprint, fewer dependencies, and the ability to leverage other services deployed at the region.  
+
+The following key services are available in Azure public MEC:
+
+- Azure Virtual Machines (Azure public MEC supports these [SKUs](key-concepts.md#azure-virtual-machines))
+- Virtual Machine Scale Sets
+- Standard public IP
+- Azure Virtual Networks
+- Virtual network peering
+- Azure Standard Load Balancer
+- Azure Kubernetes for Edge
+- Azure Bastion (must be deployed in a virtual network in the parent Azure region)
+- Azure managed disks (Azure public MEC supports Standard SSD)
+
+The following diagram explains how services are deployed at the Azure public MEC location. With this capability, enterprises and developers can deploy the customer workloads closer to their users.
+
+:::image type="content" source="./media/overview/azure-public-mec-service-deployment.png" alt-text="Diagram showing Azure public MEC service deployment.":::  
+
+## Partnership with operators
+
+Azure public MEC solutions are available in partnership with mobile network operators. The current operator partnerships are as follows:
+
+- AT&T: Atlanta, Dallas
+
+## Next steps
+
+To learn about important concepts for Azure public MEC, advance to the following article:
+
+> [!div class="nextstepaction"]
+> [Key concepts for Azure public MEC](key-concepts.md)