Post-Setup Steps

  1. If you want to use Ansys Access on Microsoft Azure in additional regions, ensure that there is a VNet in each of those regions.

    Requirements for each VNet:

    • From the VNet to the Internet:

      • Port 3389 outbound to enable communication to the Ansys Access on Microsoft Azure Control Plane and the virtual machines

      • Port 22 inbound and port 3389 inbound to facilitate connections to the virtual machines

    • From the VNet to another VNet, port 445 inbound/outbound [Optional for SMB connectivity]

    • At least one subnet

    • DNS connectivity

    • Quota for provisioning instances in the associated region

  2. If the Ansys application license server is located on a local network, ensure that it is reachable by the VNet created by the setup as well as any additional VNets that you have created.

    There must be a secure and private connection between your local network and the VNet.  Azure recommends site-to-site VPN or point-to-site VPN.  See Microsoft Azure's VPN Gateway documentation..

  3. Launch Ansys Access on Microsoft Azure and sign in with your Ansys ID.

  4. An initial project space named Onboarding Validation Project Space is created by the setup process. You can rename and use this project space if desired and/or create new project spaces to accommodate your desired usage of Ansys Access on Microsoft Azure.

Note: For known issues related to Express setup, see the Known Issues and Limitations in the Troubleshooting Guide.