Skip to main content
Veeam Service Provider Console is the portal MSPs use to manage their customers’ Veeam backups: Veeam Backup & Replication servers and their jobs, Veeam Agents, Veeam Backup for Microsoft 365 and Cloud Connect. It raises an alarm when a job fails or a server stops answering, and its alarm emails open tickets in your PSA. Connect it, and Neo agents can work those tickets from start to end.

​
What Neo can do with Veeam Service Provider Console

  • Match an alarm ticket to its triggered alarm and to the job, agent or server it is about
  • Read why a job failed: its last run, failure message and each object’s result
  • Retry a failed backup server job, or start a Veeam Agent or Microsoft 365 job again
  • Read the next run, then resolve the alarm and close the ticket, or escalate it with the cause
  • Restart a management agent, or the Veeam services on the machine through your RMM, when a connection alarm fires
  • Read repository space, protected machines and their newest restore points
  • Create and change companies, their locations, quotas, Cloud Connect and Microsoft 365 resources

​
Your companies are mapped to PSA companies

Neo matches your console companies, and your own provider organization, to the companies in your PSA and keeps the mapping on the Veeam Service Provider Console card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the company name, exact and then after stripping spaces, case and a legal-form suffix (Ltd, Inc, LLC). An AI match handles the long tail. A name two of your PSA companies share, or two console companies that match the same PSA company, gets no name match: at most an AI suggestion, which waits for you to confirm it. A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. On a ticket, an agent reaches only the console company mapped to the ticket’s company. File each alarm ticket under the customer’s company; the console names the company in each alarm email’s title (~|Company|~). A call Neo cannot tie to that one company, such as a list across every company or the console’s own settings, is for runs with no ticket company, such as a scheduled check or a chat. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. See Veeam Service Provider Console API for the permission groups.

​
Next steps

Connect Veeam Service Provider Console

Create an API key for a Neo user and save it with your console’s address.