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
Four customer AVD estates, each in its own Entra tenant and subscription.
The problem
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
- 1
Create one AvdControl organisation for the MSP, then add an Azure connection per customer Entra app.
- 2
Scope help desk to a host pool so a desk for customer A cannot see customer B.
- 3
Invite a customer business owner with help desk on only their pools. They disconnect or message without logging a ticket to the MSP.
- 4
Use seats for people who live in the console, not for every end user on AVD.
What that gives them
- 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.