This template creates all resources required to deploy a Private 5G Core, including provisioning sims and creating sample QoS policy. It can optionally be deployed to a Kubernetes cluster running on an Azure Stack Edge device.
This Azure Resource Manager (ARM) template was created by a member of the community and not by Microsoft. Each ARM template is licensed to you under a licence agreement by its owner, not Microsoft. Microsoft is not responsible for ARM templates provided and licensed by community members and does not screen for security, compatibility or performance. Community ARM templates are not supported under any Microsoft support programme or service and are made available AS IS without warranty of any kind.
Parameters
| Parameter Name | Description |
|---|---|
| location | Region where the Mobile Network will be deployed (must match the resource group region) |
| mobileNetworkName | The name for the private mobile network |
| mobileCountryCode | The mobile country code for the private mobile network |
| mobileNetworkCode | The mobile network code for the private mobile network |
| siteName | The name for the site |
| serviceName | The name of the service |
| simResources | An array containing properties of the SIM(s) you wish to create |
| simPolicyName | The name of the SIM policy |
| sliceName | The name of the slice |
| controlPlaneAccessInterfaceName | The name of the control plane interface on the access network. In 5G networks this is called the N2 interface whereas in 4G networks this is called the S1-MME interface. This should match one of the interfaces configured on your Azure Stack Edge machine. |
| controlPlaneAccessIpAddress | The IP address of the control plane interface on the access network. In 5G networks this is called the N2 interface whereas in 4G networks this is called the S1-MME interface. |
| userPlaneAccessInterfaceName | The logical name of the user plane interface on the access network. In 5G networks this is called the N3 interface whereas in 4G networks this is called the S1-U interface. This should match one of the interfaces configured on your Azure Stack Edge machine. |
| userPlaneAccessInterfaceIpAddress | The IP address of the user plane interface on the access network. In 5G networks this is called the N3 interface whereas in 4G networks this is called the S1-U interface. |
| accessSubnet | The network address of the access subnet in CIDR notation |
| accessGateway | The access subnet default gateway |
| userPlaneDataInterfaceName | The logical name of the user plane interface on the data network. In 5G networks this is called the N6 interface whereas in 4G networks this is called the SGi interface. This should match one of the interfaces configured on your Azure Stack Edge machine. |
| userPlaneDataInterfaceIpAddress | The IP address of the user plane interface on the data network. In 5G networks this is called the N6 interface whereas in 4G networks this is called the SGi interface. |
| userPlaneDataInterfaceSubnet | The network address of the data subnet in CIDR notation |
| userPlaneDataInterfaceGateway | The data subnet default gateway |
| userEquipmentAddressPoolPrefix | The network address of the subnet from which dynamic IP addresses must be allocated to UEs, given in CIDR notation. Optional if userEquipmentStaticAddressPoolPrefix is specified. If both are specified, they must be the same size and not overlap. |
| userEquipmentStaticAddressPoolPrefix | The network address of the subnet from which static IP addresses must be allocated to UEs, given in CIDR notation. Optional if userEquipmentAddressPoolPrefix is specified. If both are specified, they must be the same size and not overlap. |
| dataNetworkName | The name of the data network |
| coreNetworkTechnology | The mode in which the packet core instance will run |
| naptEnabled | Whether or not Network Address and Port Translation (NAPT) should be enabled for this data network |
| customLocation | The resource ID of the customLocation representing the ASE device where the packet core will be deployed. If this parameter is not specified then the 5G core will be created but will not be deployed to an ASE. [Collect custom location information](https://docs.microsoft.com/en-gb/azure/private-5g-core/collect-required-information-for-a-site#collect-custom-location-information) explains which value to specify here. |
Use the template
PowerShell
New-AzResourceGroup -Name <resource-group-name> -Location <resource-group-location> #use this command when you need to create a new resource group for your deploymentInstall and configure Azure PowerShell
New-AzResourceGroupDeployment -ResourceGroupName <resource-group-name> -TemplateUri https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.mobilenetwork/mobilenetwork-create-full-5gc-deployment/azuredeploy.json
Command line
az group create --name <resource-group-name> --location <resource-group-location> #use this command when you need to create a new resource group for your deploymentInstall and Configure the Azure Cross-Platform Command-Line Interface
az group deployment create --resource-group <my-resource-group> --template-uri https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.mobilenetwork/mobilenetwork-create-full-5gc-deployment/azuredeploy.json