Skip to main content
Branch preview: these instructions describe the current setup flow. Provider availability depends on the integrations enabled for your portal. Production verification is pending.
Connect a WatchGuard Cloud service-provider account to discover managed accounts, Fireboxes, and access points, with optional Endpoint Security and report data. Open Settings > Integrations, find the provider in the directory, and open its setup. You need an MSP staff account with permission to manage integrations. Company users should ask their MSP to connect the service.

Before you start

In WatchGuard Cloud, open My Account > Administration > Managed Access, enable API access, and set the read-only password. Copy the read-only Access ID, API key, and data-storage region.

Connect and map accounts

  1. In Connect, optionally enter Connection name to distinguish this connection.
  2. Choose Data-storage region. With Custom URLs, enter the Authentication API URL and API URL shown by WatchGuard; both must be HTTPS WatchGuard Cloud endpoints.
  3. Enter Read-only Access ID, Read-only password, and API key.
  4. Review Sync Fireboxes and access points, Sync Endpoint Security agents, and Capture daily Firebox report snapshots.
  5. Select Test Connection, then Create Integration. Existing connections use Save changes.
  6. Continue from Connect to start managed-account discovery. Match those accounts to the correct portal companies in the mapping step.
  7. Review device-type mapping and the available device import choices before importing devices or completing setup.
A saved credential form does not prove account discovery finished. The setup flow starts discovery when you continue from Connect, so stay on the page until that request succeeds.

Troubleshooting

  • Cannot continue from Connect: the discovery request may not have started; inspect the error and retry from the existing connection.
  • Accounts missing: confirm the credentials belong to the intended service-provider account and region.
  • An optional dataset is missing: check whether its sync option is enabled and saved.
  • Custom URL rejected: copy the HTTPS endpoints shown by WatchGuard rather than a portal login URL.