Depending on the client network setup, it may be required to add firewall rules to allow specific IBSS Guest URIs to be accessed by the app. This article provides a list of the URIs and ports needed.
⚠️ Set the time zone on the device to match the time zone for the building.
All installations
URI |
Port |
Description |
|---|---|---|
https://api.ibss.[deployment].iconics.cloud/ |
443 |
The IBSS API endpoint from which the app receives its data. |
https://storage.ibss.[deployment].iconics.cloud/ |
443 |
The IBSS storage endpoint from which the app receives its image data. |
https://api.mobile.azure.com/ |
443 |
Used for telemetry logging. |
*.appcenter.ms |
443 |
Used for telemetry logging. |
DPS installations
For setups where the ICONICS Device Provisioning Service is used, the onboarding process requires an AAD account. This requires the following URIs and ports.
| URI | Port | Description |
| https://dps.ibss.iconics.cloud/ | 443 | The ICONICS Device Provisioning Service that the app connects to on start-up. |
Non-DPS installations
For setups where the ICONICS Device Provisioning Service is not used, the onboarding process requires an AAD account. This requires the following URIs and ports.
URI |
Port |
Description |
|---|---|---|
aadcdn.msauth.net |
443 |
AAD Login |
aadcdn.msftauth.net |
443 |
AAD Login |
login.microsoftonline.com |
443 |
AAD Login |