How to use multiple Bitdefender RMM integrations at the same time
If you are migrating to a new Remote Monitoring and Management (RMM) platform, you may need to run two RMM integrations at the same time for a short period.
Bitdefender’s Remote Monitoring and Management Integration (RMMI) services connect GravityZone Control Center with third-party RMM platforms. Because RMMI services use a unified framework, the same GravityZone company ID cannot be used for multiple integrations simultaneously. The affected integrations are:
Note
Bitdefender PSA integrations (ConnectWise PSA and HaloPSA) are not affected by this limitation as they do not operate on devices or agents.
To use two RMM integrations in parallel, you must create separate partner accounts, configure each integration with its own API key, and define clear management boundaries.
If you need to run two integrations in parallel, follow these steps:
1. Create separate partner accounts
Create a unique GravityZone partner account for each RMM integration. This allows you to generate distinct API keys and configure each integration independently.
For detailed steps, see Managing user accounts.
2. Generate API keys and configure each integration
Each integration requires a separate API key for each GravityZone partner account.
Use the generated API key and the access URL to connect GravityZone to your RMM platform. Follow the specific integration guide for your platform, for example:
Repeat this process for each RMM integration you plan to use.
3. Prevent conflicts between integrations
When multiple integrations are active, they can overlap if not properly separated. To avoid conflicts in policy management, endpoint synchronization, or reporting, follow these best practices:
Assign management boundaries
Assign each RMM integration to different clients or companies. Avoid overlapping endpoint coverage.
Use unique synchronization mappings
In each integration, verify that client and site mappings are unique and do not overlap.
Create dedicated policies or groups
In GravityZone, create specific policies for each integration.
Validate synchronization health
After setup, confirm that endpoints, updates, and alerts synchronize correctly in each RMM platform. Monitor logs during the first synchronization cycles.
Example
Integration | Partner account | Managed clients |
|---|---|---|
ConnectWise Asio | Account A | Client X, Client Y |
Datto RMM | Account B | Client Z |
Recommendation
Keep a record of all partner accounts, API keys, and client mappings used for each RMM integration.