ערוך

שתף באמצעות

Create a remote network with a custom IKE policy for Global Secure Access

  • מאמר

IPSec tunnel is a bidirectional communication. This article provides the steps to set up the communication channel in Microsoft Entra admin center and the Microsoft Graph API. The other side of the communication is configured on your customer premises equipment (CPE).

Prerequisites

To create a remote network with a custom Internet Key Exchange (IKE) policy, you must have:

How to create a remote network with a custom IKE policy

If you prefer to add custom IKE policy details to your remote network, you can do so when you add the device link to your remote network. You can complete this step in the Microsoft Entra admin center or using the Microsoft Graph API.

To create a remote network with a custom IKE policy in the Microsoft Entra admin center:

  1. Sign in to the Microsoft Entra admin center as a Global Secure Access Administrator.

  2. Browse to Global Secure Access > Connect > Remote networks.

  3. Select Create remote network.

  4. Provide a name and region for your remote network and select Next: Connectivity.

  5. Select + Add a link to add the connectivity details of your CPE.

Add a link - General tab

There are several details to enter on the General tab. Pay close attention to the Peer and Local Border Gateway Protocol (BGP) addresses. The peer and local details are reversed, depending on where the configuration is completed.

Screenshot of the General tab with examples in each field.

  1. Enter the following details:

    • Link name: Name of your CPE.
    • Device type: Choose a device option from the dropdown list.
    • Device IP address: Public IP address of your device.
    • Device BGP address: Enter the BGP IP address of your CPE.
      • This address is entered as the local BGP IP address on the CPE.
    • Device ASN: Provide the autonomous system number (ASN) of the CPE.
      • A BGP-enabled connection between two network gateways requires that they have different ASNs.
      • Refer to the valid ASN values list for reserved values that can't be used.
    • Redundancy: Select either No redundancy or Zone redundancy for your IPSec tunnel.
    • Zone redundancy local BGP address: This optional field shows up only when you select Zone redundancy.
      • Enter a BGP IP address that isn't part of your on-premises network where your CPE resides and is different from Local BGP address.
    • Bandwidth capacity (Mbps): Specify tunnel bandwidth. Available options are 250, 500, 750, and 1,000 Mbps.
    • Local BGP address: Enter a BGP IP address that isn't part of your on-premises network where your CPE resides.
      • For example, if your on-premises network is 10.1.0.0/16, then you can use 10.2.0.4 as your Local BGP address.
      • This address is entered as the peer BGP​​ IP address on your CPE.
      • Refer to the valid BGP addresses list for reserved values that can't be used.

  2. Select the Next.

Add a link - Details tab

Important

You must specify both a Phase 1 and Phase 2 combination on your CPE.

  1. IKEv2 is selected by default. Currently only IKEv2 is supported.

  2. Change the IPSec/IKE policy to Custom.

  3. Select your Phase 1 combination details for Encryption, IKEv2 integrity, and DHGroup.

  4. Select your Phase 2 combinations for IPsec encryption, IPsec integrity, PFS group, and SA lifetime (seconds).

  5. Whether you choose Default or Custom, the IPSec/IKE policy you specify must match the crypto policy on your CPE.

  6. Select Next.

    Screenshot of the custom details for the device link.

  1. Enter the Pre-shared key (PSK) and Zone Redundancy Pre-shared key (PSK). The same secret key must be used on your respective CPE. The Zone Redundancy Pre-shared key (PSK) field only appears if redundancy is set on the first page in creating the link.
  2. Select Save.

Screenshot of the Security tab for adding a device link.

Next steps