Skip to content

Commit 91e5949

Browse files
committed
tabs
1 parent 5ea9371 commit 91e5949

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

articles/global-secure-access/how-to-create-remote-networks.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,11 @@ Before you can set up remote networks, you need to onboard your tenant informati
6060

6161
You MUST complete the email step before selecting the checkbox.
6262

63-
## Create a remote network with the Microsoft Entra admin center
63+
## Create a remote network
64+
65+
You can create a remote network in the Microsoft Entra admin center or through the Microsoft Graph API.
66+
67+
# [Microsoft Entra admin center](#tab/microsoft-entra-admin-center)
6468

6569
Remote networks are configured on three tabs. You must complete each tab in order. After completing the tab either select the next tab from the top of the page, or select the **Next** button at the bottom of the page.
6670

@@ -96,7 +100,7 @@ You can assign the remote network to a traffic forwarding profile when you creat
96100

97101
The final tab in the process is to review all of the settings that you provided. Review the details provided here and select the **Create remote network** button.
98102

99-
## Create remote networks using the Microsoft Graph API
103+
# [Microsoft Graph API](#tab/microsoft-graph-api)
100104

101105
Global Secure Access remote networks can be viewed and managed using Microsoft Graph on the `/beta` endpoint. Creating a remote network and assigning a traffic forwarding profile are separate API calls.
102106

@@ -163,10 +167,11 @@ Associating a traffic forwarding profile to your remote network using the Micros
163167
```
164168
165169
1. Select **Run query** to update the remote network.
170+
---
166171
167172
## Verify your remote network configurations
168173
169-
There are a few things to consider when creating remote networks.
174+
There are a few things to consider and verify when creating remote networks. You may need to double-check some settings based.
170175
171176
- **Verify IKE crypto profile**: The crypto profile (IKE phase 1 and phase 2 algorithms) set for a device link should match what has been set on the CPE. If you chose the **default IKE policy**, ensure that your CPE is set up with the crypto profile specified in the [Remote network configurations](reference-remote-network-configurations.md) reference article.
172177
@@ -175,7 +180,7 @@ There are a few things to consider when creating remote networks.
175180
- **Verify local and peer BDP IP addresses**: The public IP addresses and BGP addresses specified while creating a device link in Microsoft Global Secure Access should match what you specified when configuring the CPE.
176181
- In general, the settings in Microsoft Entra admin center and your CPE should be complementary.
177182
- Peer BGP IP addresses, such as IP1, in the Microsoft Entra admin center is a private IP address used for BGP service on your on-premise device.
178-
- Local BGP IP address, such as IP2, in the Microsoft Entra admin center is a private IP address used for BGP service on the GSA gateway.
183+
- Local BGP IP address, such as IP2, in the Microsoft Entra admin center is a private IP address used for BGP service on the Global Secure Access gateway.
179184
- You can choose the IP address for Global Secure Access that doesn't overlap with your on-premises network.
180185
- However, when setting up the on-premises device, the relationship is reversed. From the device's perspective, the peer BGP IP address is IP2, and the local BGP IP address is IP2.
181186
- The same considerations apply to ASNs.

0 commit comments

Comments
 (0)