Skip to main content

Creating XaaS Connection (Microsoft Azure Peering Service) Resources

This page describes how to create a XaaS Connection to connect to various Microsoft services via the Microsoft Azure Peering Service using the OCX Portal.

Connectable Services​

By creating a XaaS Connection (Microsoft Azure Peering Service), you can connect to Microsoft cloud services such as Microsoft 365, Dynamics 365, SaaS services, Azure, and Microsoft services accessible via the internet.

Preparation​

Please check the following before creating a XaaS Connection resource:

  • Your User Role must be either admin or user.

Procedure for Creating a XaaS Connection Resource​

  1. Log in to the OCX Portal.

  2. Click [XaaS Connections] from the left navigation bar.

  3. From the XaaS Connections list page, click [+Create], select SaaS from the menu, and then select Microsoft Peering Service.

    • This refers to the +Create icon next to the XaaS Connections title.

  4. The screen will switch to the XaaS Connection resource creation step. Configure the input items as follows and click [Create].

    • Name

      • Enter any name. Entering a name that is easy to identify makes management easier.
      • The maximum number of characters is 40.
      • Leading and trailing whitespace in the resource name will be automatically removed.

    • NAT Location

      • Select a NAT Location from the dropdown menu. Please note that the NAT Location cannot be changed after creation.
      NAT Location
      Tokyo
      Osaka
      • Note: If you select "Osaka" while 2 Gbps or 3 Gbps is selected for Speed (Bandwidth), the speed will automatically change to 1 Gbps.

    • Speed (Bandwidth)

      • If the NAT Location is "Tokyo," select any value from 1, 2, or 3 Gbps. (Support for 2 Gbps and 3 Gbps speeds started in June 2025).
        • If created with 1 Gbps, the Speed (Bandwidth) cannot be changed later.
        • If created with 2 Gbps or 3 Gbps, it cannot be changed to 1 Gbps later.
        • If the NAT Location is "Osaka," the speed is fixed at 1 Gbps.

    • Target XaaS

      • Peering Service (selected in Step 3) is displayed.

    • IPv4 Gateway Address

      • Enter the IPv4 address used as the gateway for the XaaS connection in CIDR format (IPv4/mask). (Example: 192.168.0.1/24)

    • Local ASN

      • Enter the AS number to be operated by the XaaS Connection. Private AS numbers are supported.
      • One or two instances of the local ASN will be added to the AS path of routing information.

  5. A creation confirmation popup will appear. Check the estimated cost and click [Create].

  6. The XaaS Connections list page will be displayed. Confirm that the status next to the created resource becomes available.

    • You can update the status by clicking [Refresh] in the top right corner.

This completes the creation of the XaaS Connection resource.

Once a XaaS Connection resource is created, you can perform Add NAT IP Address. Please refer to the respective operation pages for details.

Supplement​

NAT Location​

NAT Location refers to the location of the equipment providing the NAT function. Subsequent communication follows BBIX communication specifications.

NAT IP Address​

When a XaaS Connection resource is created, one Initial Assignment NAT IP Address is provided. Please check the NAT IP Address tab at the bottom of the screen. The Initial Assignment NAT IP Address cannot be deleted.

Notes​

  • With this XaaS Connection, the main communication addressed to Microsoft cloud services such as Microsoft 365, Dynamics 365, Azure, and SaaS services is available over the closed connection.
  • While the main communication is available over the closed connection, communication with certain endpoints — such as those used for authentication or for CDN services operated by companies other than Microsoft — requires a separate internet connection.
  • Connections to Windows Update and Azure VNet are not supported.
  • For details on target services and communications, please check with Microsoft.
  • Design your network to handle the number of routes advertised by Microsoft. The number of routes may change at any time according to Microsoft's specifications. Please check with Microsoft for details.
  • If you do not use an OCX-Router (v1), or if you connect via BGP between the OCX-Router (v1) and your own network equipment, you must meet the following specifications:
    • Capable of using BGP with IPv4
    • Capable of handling approximately 2000 routes or more
    • Capable of using BGP communities
    • Has a function to disable BGP enforce-first-as