IPv6 connectivity in Learn365: current support and limitations

In the modern digital landscape, IPv6 connectivity has become increasingly critical for scalability, security, and the efficient handling of growing internet traffic. For Learn365, leveraging the Azure Front Door service as part of its infrastructure means the platform benefits from native support for end-to-end IPv6 connectivity and the HTTP/2 protocol.

 

IPv6 and Azure Front Door

Azure Front Door is a global, secure entry point for web applications, offering robust features like load balancing, content acceleration, and enhanced security. A significant advantage of Azure Front Door is its native support for end-to-end IPv6 connectivity.

For Learn365, this means users and APIs accessing the platform can rely on the underlying Azure Front Door to support IPv6 when applicable. Additionally, support for the HTTP/2 protocol improves performance, reduces latency, and allows better resource management over connections, further enhancing the user experience.

For more information about Azure Front Door, see this Microsoft article.

 

Current IPv6 support in Learn365

While the Learn365 platform benefits from Azure Front Door's IPv6 capabilities, its adoption of IPv6 is currently partial. The following domains support IPv6 connectivity:

  • Learn365 API domains. All APIs accessed through Learn365 domains are fully accessible over IPv6.
  • Learn365 assets domains. Any static assets hosted for Learn365 are IPv6-compatible.
  • Learn365 core domain (lms.365.systems). This domain for the Learn365 platform supports IPv6 connectivity.

For the following regional Learn365 domains, IPv6 is supported via Azure IPv6 implementation in App Service, which is currently in public preview:

  • ne-lms.365.systems (North Europe)
  • au-lms.365.systems (Australia East)
  • ch-lms.365.systems (Switzerland)
  • ca-lms.365.systems (Canada Central)
  • us-lms.365.systems (Central US)
  • je-lms.365.systems (Japan East)

 

Limitations: regional domains

IPv6 support isn't yet extended to regional domains such as:

  • de-lms.365.systems (Germany West Central)
  • uk-lms.365.systems (UK South)

These regional domains rely solely on IPv4 at this time, which may impact users and applications requiring end-to-end IPv6 connectivity in specific geographies. Azure IPv6 implementation in App Service isn't currently available in these regions.

For more information about support for IPv6, see this Azure App Service article.

 

Future outlook

As IPv6 adoption continues to grow globally, we are planning to expand IPv6 support to all regional domains, ensuring consistent connectivity and compatibility across all areas of the platform.

 

Was this article helpful?
0 out of 0 found this helpful