From the Fleet Service Point page, you can download the required Fleet Service Point files to provision your Fleet Service Point to your VMware environment, Azure environment, or Cisco ENCS devices.
If you are provisioning on VMware, you can download the OVA image of the Fleet Service Point and the associated checksum file. The OVA image can be reused to provision multiple Fleet Service Points in your environment; however, you can only apply one Fleet Service Point configuration per Fleet Service Point image. Once you have created the Fleet Service Point within the Edge Cloud, you can download the base64-encoded configuration JSON file that will be used to register the Edge Fleet Service Point to the DNS Edge Cloud. Once the Edge Fleet Service Point has registered in the DNS Edge Cloud, you can provision the DNS resolver service.
If you are provisioning on Azure, you must create the Fleet Service Point through the Edge Cloud. Once created, you can are presented with a base64 encoded configuration text file that contains information that will be used to register the Edge Fleet Service Point to the DNS Edge Cloud. Once the Edge Fleet Service Point has been provisioned on Azure and registered in the DNS Edge Cloud, you can deploy the DNS resolver service.
Once you have provisioned the Fleet Service Point with a registration key and registration endpoint, the values are invalidated and cannot be used again to provision another Fleet Service Point.
In the top navigation bar, click 
and select Fleet Service
Points. A new tab opens with the Fleet Service Points overview page.
The Fleet Service Points overview page shows a list of Edge Fleet Service Points that were previously provisioned. You can click the name of an Edge Fleet Service Point to display additional information.