Managed service

MSP operations across several customer AVD estates

A managed service provider needed one console for several customer Entra tenants, and a way to let a customer business team act on their own pools.

Example setup for this sector. Not a named customer, and not a results claim.

The estate

What they were running

Four customer AVD estates, each in its own Entra tenant and subscription.

The problem

Why the queue filled up

Engineers jumped between Azure Portal directories to find a session. Tickets stalled when the wrong subscription was selected. Customers asked who had logged a user off, and some wanted their own line managers to act without raising a ticket.

What they set up

The same four moves, scoped to this estate.

  1. 01

    Create one AvdControl organisation for the MSP, then add an Azure connection per customer Entra app.

  2. 02

    Scope help desk to a host pool so a desk for customer A cannot see customer B.

  3. 03

    Invite a customer business owner with help desk on only their pools. They disconnect or message without logging a ticket to the MSP.

  4. 04

    Use seats for people who live in the console, not for every end user on AVD.

What that gives them

A clearer way to act.

  • One place to pick a customer connection and see that estate only.
  • The customer can clear a stuck session on their pool without a ticket.
  • Log off and disconnect stay on the record for the customer audit.

More scenarios

All case studies
Coming soon

Connect Azure, pick pools, then delegate.

Self-serve signup will open shortly. Get in touch for early access.