Skip to main content
NinjaOne SaaS Backup, formerly Dropsuite, backs up your clients’ Microsoft 365 and Google Workspace: mail, calendars, contacts, tasks, OneDrive, SharePoint, Teams and Groups, Google Drive and shared drives. Each client is an organization in your Partner Portal. Connect it, and Neo agents can report every client’s backups, seats and accounts, and check a backup on a ticket. Neo only reads NinjaOne SaaS Backup. It does not add mailboxes, change seats or start restores; an agent tells the technician what to change in the Partner Portal.

What Neo can do with NinjaOne SaaS Backup

  • Backup status. Read the status, last backup and error of every mailbox, OneDrive, SharePoint site, Team and Google Drive.
  • Seats and storage. Read each organization’s seats used and bought, active and deactivated seats, shared mailboxes and storage.
  • Accounts and tenants. List active, deactivated and deleted accounts, each Microsoft 365 or Google Workspace tenant, and the mailboxes in a tenant that are not backed up yet.
Common uses:
  • Backup status report. List each client’s failed or stale backups and why, on a schedule or when you ask in chat.
  • Seat billing check. Compare each client’s seats used with the seats bought, and with the quantity on the client’s agreement in your PSA.
  • Active accounts report. List each client’s active, deactivated and unprotected mailboxes.
Neo reads seats, not prices or invoices: NinjaOne SaaS Backup sends its invoice through Xero.

Your organizations are mapped to companies

Neo matches your NinjaOne SaaS Backup organizations to the companies in your PSA and keeps the mapping on the card’s Organization Mapping tab, refreshed on each PSA metadata sync. Neo tries three ways, strongest first:
  1. The organization’s name, exact and then after stripping spaces, case and a legal-form suffix (Ltd, Inc, LLC). A name two of your PSA companies share, or two organizations that match the same company, gets no name match.
  2. The owner email’s domain, against your PSA companies’ websites. A domain that two organizations’ owners use, such as your own when you sign clients up with your address, matches neither.
  3. An AI match for the rest.
A name match, or one you confirm, is handed straight to your agents. A domain match and an AI match are not: each shows on the Organization Mapping tab, where you confirm or correct it. On a ticket, an agent reaches only the organization mapped to the ticket’s company. A ticket filed under your own company reaches no organization, so set the ticket’s company to the client first. The list of every organization is for runs with no ticket company, such as a scheduled report or a chat. Anything Neo could not match stays unmapped and visible on the same tab, where you set the right company by hand. A mapping you set by hand survives every later sync.

What Neo hides

Every NinjaOne SaaS Backup answer that carries a token, such as each organization’s authentication token, reads [hidden by Neo] before an agent sees it. Neo never sends the three calls that create a single sign-on link into a portal; a technician signs in through the Partner Portal.

Next steps

Connect NinjaOne SaaS Backup

Copy the API URL and the two tokens from API Settings and save them in Neo.