2.x support for multiple Azure subscriptions/tenants?

[christiankelly]

This KB https://www.veeam.com/kb3122 references 1.x, is this the same for 2.x?

Any thoughts about service providers using VBA to backup multiple clients/subscriptions?

[dalbertson]

It does still apply. Lighthouse would be the path for a SP at this moment

[christiankelly]

When you say "lighthouse" what design are you actually talking about? Would the idea be you install an appliance per client under the service provider"? Or would you install the appliance under each client's subscription?

[frankive]

Hi.

Is it possible for an Veeam Backup for Azure installation to backup VMs in other tenant or is it one-tenant only?
I presumre it will work on multple subscriptions within a tenant, but cant quite find any documentation saying something about a multi-tenant configuration.

As a service provider, you know what we would like to achieve........

[HannesK]

Hello,
are you using Azure Lighthouse (see above)?

Best regards,
Hannes

[frankive]

yes, we are using lighthouse to see the status for Defender over all the 365-tenants.
How can we use lighthouse in the matter of Veeam Azure Backup?
We will have to install an appliance in each customertenant?

[frankive]

Hmm, from what I can understand we only need to deploy this in the service providers tenant as long as we do have lighthouse down to the customer? Any nice blogs on this usecase? Would be great to not manage a whole lot of different implementations of Veeam Azure for Backup for each customer?

[Vitaliy S.]

Hi Frank,

There are no blogs on this, but thanks for your feedback, we will discuss it internally. As regards your questions, then deploying in tenant's subscription will allow you to isolate the activity, but if you want to deploy it in your subscription that's all possible. In the later case, you will need to create policies per tenant as it will allow you to have some sort of multi-tenancy within the VB application.

Thanks!

[bertdhont]

We have Veeam Backup for Azure running in our subscription.
We use lighthouse, so we can access the tentants of our customers to take care of their backup in Azure.
But what we notice is that we can only see the tentants that where there when we deployed the Azure AD application. Is it normal that tenants (and subscriptions) that are added after the initial setup, are not automatically discovered?
Do we have to edit the service account to make the new subscriptions visible?

[Vitaliy S.]

Hi Bert,

That's a good question, most likely it is by-design as we don't want to query discovery APIs (that cost money) when those are not needed. Can you please tell us how frequently do you add new clients and how do you monitor them, report on policy status, and generate invoices for backup services?

Thanks!