To use the Priva Services, it must be possible to communicate with the Priva Cloud. The network must allow this communication in, for instance, firewalls and routers. It must be possible to use the ports for the protocols. Communication with the Priva Cloud must also be permitted. This may be based on the IP addresses or on the Fully Qualified Domain Names that are required for the Priva Services. Finally, the apps and URLs that are used for Priva Services may not be blocked.
The table below lists the port numbers for Priva Services:
|Priva Service||Port 443
|Priva Access Control||√|
|Priva Spaces API||√||√||√||√||√|
Note: All ports only use outgoing communication.
¹ TC Manager Connect starts an HTTP connection with the local webserver on the PC, which then set up an HTTPS connection to the cloud via an API.
The list below shows the Fully Qualified Domain Names (FQDN) that are required for Priva Cloud services. You have the choice to use wildcards (addresses starting with *) or to release the full FQDNs. However, the list of full FQDNs is dynamic; FQDNs can be added in the future and they can be changed.
- Until August 22, 2020: rdc-prd-backend-ih-we.azure-devices.net
From August 22, 2020: prd-priva-generic-ih.azure-devices.net
Priva uses the "EuropeWest" IP address ranges from Microsoft that are required for Priva Cloud services. These series are used dynamically by Microsoft and therefore can not be mentioned specifically. The series that Microsoft uses, can be found on their website under 'Microsoft Azure Datacenter IP Ranges' https://www.microsoft.com/en-us/download/details.aspx?id=41653