Skip to content

Commit 78bf293

Browse files
authored
Merge pull request #218570 from b-branco/west-europe-support
Add support for West Europe region
2 parents a802d8f + c164f70 commit 78bf293

11 files changed

+50
-15
lines changed

articles/private-5g-core/collect-required-information-for-a-site.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,8 @@ Collect all the values in the following table for the mobile network site resour
2929
|The Azure subscription to use to create the mobile network site resource. You must use the same subscription for all resources in your private mobile network deployment. |**Project details: Subscription**|
3030
|The Azure resource group in which to create the mobile network site resource. We recommend that you use the same resource group that already contains your private mobile network. |**Project details: Resource group**|
3131
|The name for the site. |**Instance details: Name**|
32-
|The region in which you’re creating the mobile network site resource. We recommend that you use the East US region. |**Instance details: Region**|
32+
|The region in which you deployed the private mobile network. |**Instance details: Region**|
33+
|The [region code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*. </br></br>You only need to collect this value if you're going to create your site using an ARM template. |Not applicable.|
3334
|The mobile network resource representing the private mobile network to which you’re adding the site. |**Instance details: Mobile network**|
3435
|The billing plan for the site that you are creating. The available plans have the following allowances:</br></br> G1 - 1 Gbps per site and 100 devices per network. </br> G2 - 2 Gbps per site and 200 devices per network. </br> G3 - 3 Gbps per site and 300 devices per network. </br> G4 - 4 Gbps per site and 400 devices per network. </br> G5 - 5 Gbps per site and 500 devices per network.|**Instance details: Site plan**|
3536

articles/private-5g-core/collect-required-information-for-private-mobile-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Collect all of the following values for the mobile network resource that will re
3030
|The Azure subscription to use to deploy the mobile network resource. You must use the same subscription for all resources in your private mobile network deployment. You identified this subscription in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md). |**Project details: Subscription**
3131
|The Azure resource group to use to deploy the mobile network resource. You should use a new resource group for this resource. It's useful to include the purpose of this resource group in its name for future identification (for example, *contoso-pmn-rg*). |**Project details: Resource group**|
3232
|The name for the private mobile network. |**Instance details: Mobile network name**|
33-
|The region in which you're deploying the private mobile network. We recommend you use the East US region. |**Instance details: Region**|
33+
|The region in which you're deploying the private mobile network. This can be the East US or the West Europe region. |**Instance details: Region**|
3434
|The mobile country code for the private mobile network. |**Network configuration: Mobile country code (MCC)**|
3535
|The mobile network code for the private mobile network. |**Network configuration: Mobile network code (MNC)**|
3636

articles/private-5g-core/configure-service-sim-policy-arm-template.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ If your environment meets the prerequisites and you're familiar with using ARM t
2424

2525
- Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the built-in Contributor or Owner role at the subscription scope.
2626
- Identify the name of the Mobile Network resource corresponding to your private mobile network and the resource group containing it.
27+
- Identify the Azure region in which you deployed your private mobile network.
2728
- Identify the name of the data network to which you want to assign the new policy.
2829
- The ARM template is populated with values to configure a default service and SIM policy that allows all traffic in both directions.
2930

@@ -50,8 +51,8 @@ Two Azure resources are defined in the template.
5051

5152
- **Subscription:** select the Azure subscription you used to create your private mobile network.
5253
- **Resource group:** select the resource group containing the Mobile Network resource representing your private mobile network.
53-
- **Region:** select **East US**.
54-
- **Location:** enter *eastus*.
54+
- **Region:** select the region in which you deployed the private mobile network.
55+
- **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*.
5556
- **Existing Mobile Network Name:** enter the name of the Mobile Network resource representing your private mobile network.
5657
- **Existing Slice Name:** enter **slice-1**.
5758
- **Existing Data Network Name:** enter the name of the data network. This value must match the name you used when creating the data network.

articles/private-5g-core/create-overview-dashboard.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ If your environment meets the prerequisites and you're familiar with using ARM t
2828

2929
- The name of the **Kubernetes - Azure Arc** resource that represents the Kubernetes cluster on which your packet core instance is running.
3030
- The name of the resource group containing the **Kubernetes - Azure Arc** resource.
31+
- The Azure region in which you deployed your private mobile network.
3132

3233
## Review the template
3334

@@ -45,7 +46,7 @@ The template defines one [**Microsoft.Portal/dashboards**](/azure/templates/micr
4546

4647
- **Subscription:** set this to the Azure subscription you used to create your private mobile network.
4748
- **Resource group:** set this to the resource group in which you want to create the dashboard. You can use an existing resource group or create a new one.
48-
- **Region:** select **East US**.
49+
- **Region:** select the region in which you deployed the private mobile network.
4950
- **Connected Cluster Name:** enter the name of the **Kubernetes - Azure Arc** resource that represents the Kubernetes cluster on which your packet core instance is running.
5051
- **Connected Cluster Resource Group:** enter the name of the resource group containing the **Kubernetes - Azure Arc** resource.
5152
- **Dashboard Display Name:** enter the name you want to use for the dashboard.

articles/private-5g-core/create-site-arm-template.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,8 @@ Four Azure resources are defined in the template.
5252
|--|--|
5353
| **Subscription** | Select the Azure subscription you used to create your private mobile network. |
5454
| **Resource group** | Select the resource group containing the mobile network resource representing your private mobile network. |
55-
| **Region** | Select **East US**. |
56-
| **Location** | Enter *eastus*. |
55+
| **Region** | Select the region in which you deployed the private mobile network. |
56+
| **Location** | Enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*. |
5757
| **Existing Mobile Network Name** | Enter the name of the mobile network resource representing your private mobile network. |
5858
| **Existing Data Network Name** | Enter the name of the data network. This value must match the name you used when creating the data network. |
5959
| **Site Name** | Enter a name for your site.|

articles/private-5g-core/deploy-private-mobile-network-with-site-arm-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The following Azure resources are defined in the template.
6767
|---------|---------|
6868
|**Subscription** | Select the Azure subscription you want to use to create your private mobile network. |
6969
|**Resource group** | Create a new resource group. |
70-
|**Region** | Select **East US**. |
70+
|**Region** | Select the region in which you're deploying the private mobile network. |
7171
|**Location** | Leave this field unchanged. |
7272
|**Mobile Network Name** | Enter a name for the private mobile network. |
7373
|**Mobile Country Code** | Enter the mobile country code for the private mobile network. |

articles/private-5g-core/manage-sim-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ To create a new SIM group:
4343
1. Do the following on the **Basics** configuration tab.
4444

4545
- Enter a name for the new SIM group into the **SIM group name** field.
46-
- Set **Region** to **East US**.
46+
- In the **Region** field, select the region in which you deployed the private mobile network.
4747
- Select your private mobile network from the **Mobile network** drop-down menu.
4848

4949
:::image type="content" source="media/manage-sim-groups/create-sim-group-basics-tab.png" alt-text="Screenshot of the Azure portal showing the Basics configuration tab.":::

articles/private-5g-core/provision-sims-arm-template.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ If your environment meets the prerequisites and you're familiar with using ARM t
2424

2525
- Ensure you can sign in to the Azure portal using an account with access to the active subscription you identified in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md). This account must have the built-in Contributor role at the subscription scope.
2626
- Identify the name of the Mobile Network resource corresponding to your private mobile network and the resource group containing it.
27+
- Identify the Azure region in which you deployed your private mobile network.
2728
- Choose a name for the new SIM group to which your SIMs will be added.
2829
- Identify the SIM policy you want to assign to the SIMs you're provisioning. You must have already created this SIM policy using the instructions in [Configure a SIM policy - Azure portal](configure-sim-policy-azure-portal.md).
2930

@@ -86,21 +87,21 @@ The following Azure resources are defined in the template.
8687

8788
- **Subscription:** select the Azure subscription you used to create your private mobile network.
8889
- **Resource group:** select the resource group containing the Mobile Network resource representing your private mobile network.
89-
- **Region:** select **East US**.
90-
- **Location:** enter *eastus*.
90+
- **Region:** select the region in which you deployed the private mobile network.
91+
- **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*.
9192
- **Existing Mobile Network Name:** enter the name of the Mobile Network resource representing your private mobile network.
9293
- **Existing Sim Policy Name:** enter the name of the SIM policy you want to assign to the SIMs.
9394
- **Sim Group Name:** enter the name for the new SIM group.
9495
- **Sim Resources:** paste in the array you prepared in [Prepare an array for your SIMs](#prepare-an-array-for-your-sims).
9596

9697
:::image type="content" source="media/provision-sims-arm-template/sims-arm-template-configuration-fields.png" alt-text="Screenshot of the Azure portal showing the configuration fields for the SIMs ARM template.":::
9798

98-
1. Select **Review + create**.
99-
1. Azure will now validate the configuration values you've entered. You should see a message indicating that your values have passed validation.
99+
2. Select **Review + create**.
100+
3. Azure will now validate the configuration values you've entered. You should see a message indicating that your values have passed validation.
100101

101102
If the validation fails, you'll see an error message and the **Configuration** tab(s) containing the invalid configuration will be flagged. Select the flagged tab(s) and use the error messages to correct invalid configuration before returning to the **Review + create** tab.
102103

103-
1. Once your configuration has been validated, you can select **Create** to provision your SIMs. The Azure portal will display a confirmation screen when the SIMs have been provisioned.
104+
4. Once your configuration has been validated, you can select **Create** to provision your SIMs. The Azure portal will display a confirmation screen when the SIMs have been provisioned.
104105

105106
## Review deployed resources
106107

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Region code names for Azure Private 5G Core
3+
description: Learn about the region code names used for the location parameter in Azure Private 5G Core ARM templates
4+
author: b-branco
5+
ms.author: biancabranco
6+
ms.service: private-5g-core
7+
ms.topic: reference
8+
ms.custom: references_regions
9+
ms.date: 11/17/2022
10+
---
11+
12+
# Region code names
13+
14+
When the **location** parameter is used in a command or request, you need to provide the region code name as the **location** value. To get the code name of the region that your private mobile network is in, run the following command in the Azure CLI.
15+
16+
```cloudshell-bash
17+
az account list-locations -o table
18+
```
19+
20+
The output of this command is a table of the names and locations for all the Azure regions that your subscription supports. Navigate to the Azure region that has the *DisplayName* you are looking for and use its *Name* value for the **location** parameter.
21+
22+
For example, if you're deploying in the East US region, use *eastus* for the **location** parameter.
23+
24+
```json
25+
DisplayName Name RegionalDisplayName
26+
------------------------ ------------------- -------------------------------------
27+
East US eastus (US) East US
28+
West Europe westeurope (Europe) West Europe
29+
```

articles/private-5g-core/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,8 @@ items:
120120
items:
121121
- name: REST API
122122
href: /rest/api/mobilenetwork
123+
- name: Region code names
124+
href: region-code-names.md
123125
- name: Resources
124126
items:
125127
- name: Azure Private 5G Core product page

0 commit comments

Comments
 (0)