Skip to content

Commit d42bd9b

Browse files
committed
remove a note
1 parent b6a3af4 commit d42bd9b

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

articles/internet-peering/howto-legacy-direct-portal.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
22
title: Convert a legacy Direct peering to an Azure resource - Azure portal
3-
description: Convert a legacy Direct peering to an Azure resource using the Azure portal.
4-
services: internet-peering
3+
titleSuffix: Internet Peering
4+
description: Learn how to convert a legacy Direct peering to an Azure resource using the Azure portal.
55
author: halkazwini
6+
ms.author: halkazwini
67
ms.service: internet-peering
78
ms.topic: how-to
8-
ms.date: 01/23/2023
9-
ms.author: halkazwini
10-
ms.custom: template-how-to, engagement-fy23
9+
ms.date: 10/03/2023
1110
---
1211

1312
# Convert a legacy Direct peering to an Azure resource using the Azure portal
@@ -42,9 +41,6 @@ As an Internet Service Provider, you can convert legacy direct peering connectio
4241

4342
* For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
4443

45-
>[!NOTE]
46-
>Once a subscription and resource group have been selected for the peering resource, it cannot be moved to another subscription or resource group.
47-
4844
* Name corresponds to the resource name and can be anything you choose.
4945

5046
* Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.

0 commit comments

Comments
 (0)