- 11 Nov 2025
- 2 Minutes to read
- Print
- PDF
Firewall Settings for Scalefusion
- Updated on 11 Nov 2025
- 2 Minutes to read
- Print
- PDF
Scalefusion is a cloud-hosted solution with servers across the continents. This means devices enrolled and managed by Scalefusion need to have continuous access to Scalefusion's servers so that they can be managed in real-time. The devices also need to have a connection with Google Push services, Apple Push services and Windows Push services, along with other components that are required for the management of devices. Also, to access Scalefusion's Dashboard, the PC/Laptop needs to have access to certain IPs and URLs.
However, an organization might be restricting internet access on their corporate-managed devices and/or PCs/Laptops by using a firewall or a proxy. In such cases, it becomes important to allow the URLs, IPs and ports required for Scalefusion to work smoothly in your organization.
This guide outlines the Firewall settings that need to be done for Scalefusion and OneIdP.
Scalefusion Instances
To comply with data residency regulations, Scalefusion operates multiple regional instances:
Instance Name | URL | Location |
|---|---|---|
Global (EU) | EU | |
US | USA | |
India | India | |
MEA | UAE |
Ensure firewall rules are applied according to the instance your organization uses.
General Firewall Requirements (All Regions)
URL/Domain/FQDN | Ports | Protocol | Direction | Description |
|---|---|---|---|---|
80, 443 | HTTP/S | Outbound | Main domain for API and dashboard access. | |
80, 443 | HTTP/S | Outbound | Core Scalefusion services. | |
Google FCM/GCM | 5228-5230 | TCP | Outbound | Google GCM/FCM push notification connectivity. |
*.pushy.me | 443 | HTTPS | Outbound | Pushy messaging domains |
*.pushy.io | 443 | HTTPS | Outbound | Pushy messaging domains |
Recommendation: Whitelist wildcard domains to simplify firewall maintenance and include all current and future subdomains.
Device Platform Specific Firewall Settings
Android
URL/Domain/FQDN | Ports | Protocol | Direction | Description |
|---|---|---|---|---|
Android Enterprise Docs | - | - | Outbound | |
Samsung Knox | - | - | Outbound | |
443 | HTTPS | Outbound | Lenovo device activation URL. | |
443 | HTTPS | Outbound | OS device enrollment. |
Google GCM/FCM IPs: Allow all IPs from Google's ASN 15169 (Google ASN IP list) due to frequent IP changes.
iOS and macOS
Follow Apple’s official firewall guidelines for Push Notifications:
Apple Push Notifications Firewall Configuration
Windows
URL/Domain | Port | Protocol | Direction | Description |
|---|---|---|---|---|
| 443 | HTTPS | Outbound | Windows “Access to School or Work” services |
| 443 | HTTPS | Outbound | Windows notification services |
| 443 | HTTPS | Outbound | Windows notification services |
| 443 | HTTPS | Outbound | Device login services |
| 443 | HTTPS | Outbound | Device management portal |
| 443 | HTTPS | Outbound | Enrollment endpoints |
| 443 | HTTPS | Outbound | IP-based device location |
| 443 | HTTPS | Outbound | Windows Information Protection service |
Windows Update Delivery Optimization:
See Microsoft’s documentation for URLs and ports required for update optimization and delivery:Ports: 7680 (TCP), 3544 (UDP), 443 (HTTPS)
Domains: .prod.do.dsp.mp.microsoft.com, .dl.delivery.mp.microsoft.com, *.windowsupdate.com, etc.
Certificate Validation Endpoints (All Regions)
Domain | Port | Protocol | Direction | Description |
|---|---|---|---|---|
| 443 | HTTPS | Outbound | Certificate revocation checks |
| 443 | HTTPS | Outbound | OCSP verification (primary) |
| 443 | HTTPS | Outbound | OCSP verification (secondary) |
Important: Blocking these may cause SSL/TLS trust errors for Scalefusion services.
Scalefusion Core and Service Endpoints
Common Service Endpoints (Global)
URL/Domain | Ports | Protocol | Direction | Description |
|---|---|---|---|---|
| 80, 443 | HTTP/S | Outbound | Core Scalefusion API |
| 80, 443 | HTTP/S | Outbound | Device enrollment and provisioning |
| 80, 443 | HTTP/S | Outbound | EVA Assistant services |
| 80, 443 | HTTP/S, UDP | Outbound | Remote Cast/Control signaling |
| 80, 443 | HTTP/S | Outbound | IoT device connector |
| 8883 | MQTT/TLS | Outbound | IoT communication |
| 80, 443 | HTTP/S, WSS | Outbound | Remote Terminal access |
| 80, 443 | HTTP/S | Outbound | Secure Web Gateway (Veltar/WCF) services |
Use corresponding regional prefixes for India (
*-in), MEA (*-mea), and US (endpointlockdown.com) instances.
OneIdP Firewall Settings
Instance | URL/Domain | Port | Protocol | Direction | Description |
|---|---|---|---|---|---|
Global |
| 443 | HTTPS | Outbound | Core authentication & SSO services |
US |
| 443 | HTTPS | Outbound | US regional OneIdP services |
India |
| 443 | HTTPS | Outbound | India regional OneIdP services |
MEA |
| 443 | HTTPS | Outbound | MEA regional OneIdP services |
Content Delivery and CDN URLs by Region
Region | URL/Domain/FQDN (Scalefusion) | URL/Domain/FQDN (OneIdP) | Port | Protocol | Description |
|---|---|---|---|---|---|
Global (EU) | 443 | HTTPS | Content Management, App Management, Branding | ||
443 | HTTPS | CDN Edge server for APK distribution | |||
US | 443 | HTTPS | Content Management, App Management, Branding | ||
443 | HTTPS | CDN Edge server for APK distribution | |||
India | 443 | HTTPS | Content Management, App Management, Branding | ||
443 | HTTPS | CDN Edge server for APK distribution | |||
MEA | https://scalefusion-mea-assets-oneidp.s3.me-central-1.amazonaws.com | 443 | HTTPS | Content Management, App Management, Branding | |
443 | HTTPS | CDN Edge server for APK distribution |
Webhook & Integration IPs (Outbound Server Connections)
Region | Instance | IP Address | Purpose |
|---|---|---|---|
Global (EU) |
|
| Webhooks & integrations |
India |
|
| Webhooks & integrations |
MEA |
|
| Webhooks & integrations |
US |
|
| Webhooks & integrations |
Note: IPs may change without prior notice. Ensure both inbound and outbound rules allow these addresses.
Additional Notes
TLS Support: Scalefusion supports TLSv1.2 and TLSv1.3 only; ensure your firewall permits traffic over these protocols.
Allow wildcard subdomains (e.g., *.mobilock.in) where applicable for smoother updates.
Regular updates to firewall rules may be necessary, especially for Microsoft IP ranges and Google ASN blocks.
