Skip to content
Current

NinjaOne SaaS Backup (Dropsuite): Microsoft 365 and Google Workspace backups per partner

Paste the API URL and two tokens from Dropsuite's API Settings, and Current brings each partner's cloud backups onto the company record: which mailboxes, OneDrives, SharePoint sites, Teams and Google Drives are backed up, which are failing or have had no good backup for two days, and the storage used. The sync only reads Dropsuite.

Updated 6 min read
On this page · 3 sections

Dropsuite, also sold as NinjaOne SaaS Backup, backs up your partners' Microsoft 365 and Google Workspace accounts: mailboxes, OneDrive, SharePoint sites, Teams and Groups, and Google Drive. This connector reads that estate into Current every 30 minutes and hangs each organization off the matching company, so you can see which accounts are backed up, which are failing, and how much storage each partner uses. It is a reporting feed: the sync reads Dropsuite and changes nothing in it. It never restores, adds or removes a seat, or creates an organization.

Note
Not yet checked against a live account
This connector is unverified. It was built from Dropsuite's published API shapes, because Dropsuite's own API guide sits behind a NinjaOne sign-in, and it hasn't been checked against a live Dropsuite account yet. The first sync records what Dropsuite actually sends. If a count on the company record looks wrong, tell us and we'll correct it.

Connect it

  1. 1
    Open API Settings
    Sign in to the Dropsuite Partner Portal (NinjaOne SaaS Backup) as an administrator and open Settings, then API Settings. API access is available only to Direct Partners and Distributors; if you buy through someone else, ask them to turn it on.
  2. 2
    Copy three values
    Copy the API URL, the Reseller Token and the Authentication Token from the API Information section.
  3. 3
    Paste and test
    In Current open Integrations, find NinjaOne SaaS Backup (Dropsuite) under Backup, paste all three and press Test connection.
  4. 4
    Check the matches
    After the first sync, check the mapping list: each organization is matched to a company by name, or by its email domain against the company's website. Fix any that are wrong.
Note
Where your tokens can go
Current only sends your tokens to a Dropsuite API address it recognises (dropsuite.us, dropsuite.com and its regions, the NinjaOne SaaS Backup addresses ending in backup.ninjarmm.com, and Dropsuite's European addresses). A URL anywhere else is refused before anything is sent. Leave a token field empty when you save again to keep the token you saved before.

What Current syncs

Data setWhat Current storesWhere it lands
OrganizationsEach Dropsuite customer organization by name, its seat and shared mailbox counts, its storage used, and whether it is suspendedThe mapping list on the card, and the company's backup card
Backed-up accountsEach mailbox, OneDrive, SharePoint site, Team or Group and Google Drive: the address or name the backup covers, Dropsuite's status, whether Dropsuite reported an error, the last backup and the last good backup, and whether it is failing or staleThe company's backup card, the backups-failing alert and business reviews

Failing and stale

An account is failing when Dropsuite reports Connection Failed, Authentication Error or System Error, when a backup completed with errors, or when it has had no good backup for 48 hours (stale). A deactivated account is not counted either way. An account added in the last two days that has not finished its first backup is shown as not known yet rather than failing. The same definition drives the company card, the backups-failing alert and business reviews.

Note
What Current never keeps
Current never reads or stores mailbox content, file names, display names or usernames, and keeps no token for any one customer: each customer's own access token is used during a sync and then dropped. Dropsuite's error text is not stored either, only whether there was one. The address a mailbox backup covers is visible to your staff only where they work on that partner, never in reports or exports. Partner (read-only) viewers never see any of this data; it is blocked at the database, not just hidden.
Note
Who can do this, and disconnecting
Connecting, testing, Sync now, mapping and disconnecting are Tenant Admin actions. Disconnect stops the sync; the figures already read stay and stop updating, and reconnecting resumes with your mappings intact. Disconnecting doesn't revoke the tokens in Dropsuite; regenerate them there to retire them.
Was this helpful?