Skip to content

Commit ac0f6fe

Browse files
committed
fixed note
1 parent 4e667bc commit ac0f6fe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/expressroute/expressroute-howto-routing-portal-resource-manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,8 @@ This section helps you create, get, update, and delete the Microsoft peering con
7474
* AS number for peering. You can use both 2-byte and 4-byte AS numbers.
7575
* Advertised prefixes: You provide a list of all prefixes you plan to advertise over the BGP session. Only public IP address prefixes are accepted. If you plan to send a set of prefixes, you can send a comma-separated list. These prefixes must be registered to you in an RIR / IRR.
7676

77-
> [!NOTE]
78-
> For each configured prefix, Microsoft generates a **Validation ID**. The organization that owns the prefixes will use this ID to verify their authority to advertise the prefixes. Detailed verification steps are provided in the next section.
77+
> [!NOTE]
78+
> For each configured prefix, Microsoft generates a **Validation ID**. The organization that owns the prefixes will use this ID to verify their authority to advertise the prefixes. Detailed verification steps are provided in the next section.
7979
8080
* **Optional -** Customer ASN: If you're advertising prefixes not registered to the peering AS number, you can specify the AS number to which they're registered with.
8181
* Routing Registry Name: You can specify the RIR / IRR against which the AS number and prefixes are registered.

0 commit comments

Comments
 (0)