Mailboxes not licensed? | 1.5.0.1309

[prewest]

Hi,

On a clean installation of a Veeam Office 365 I get the error that my some of our Office 365 are not licensed?
I already tried to open port 9192 as this topic https://forums.veeam.com/veeam-backup-f ... 44527.html mentioned.
That did not work,

Now only 2 mailboxes are being backupped, the rest says "mailbox not licensed".

Any help?

I am using version 1.5.0.1309

[Mike Resseler]

Hi Arnold,

Can you do a get-mailbox PowerShell command to your organization? Mailbox not licensed normally means that you don't have a MSFT license attached to it. We need that license otherwise the connection API's don't work. This is only for user mailboxes, shared mailboxes, group mailboxes work differently

Let me know

[prewest]

Hi Mike,

Yes, I can do that.
I get a complete list of all my users.

Also if I check my license status with "Get-MsolAccountSky" I see no warnings at all.
All accounts are licensed.

RecipientType : UserMailbox

Hi Arnold,

Can you do a get-mailbox PowerShell command to your organization? Mailbox not licensed normally means that you don't have a MSFT license attached to it. We need that license otherwise the connection API's don't work. This is only for user mailboxes, shared mailboxes, group mailboxes work differently

Let me know

[Helferlein]

I had the same on some users and solved it as follows:

1.) Login to O365 User Portal
2.) Open an affected User
3.) Took away the O365 License from the User whithout clicking on apply
4.) Assign again the O365 License to the User
5.) Click now on apply
6.) Wait an hour to be sure
7.) Try to backup with Veeam O365 again

I solved like 5 users that way.

[Mike Resseler]

Hi Peter,

Thank you for this information. Do you have any idea what was wrong in your case? While I am very glad it helped in your case, I am having trouble understanding the why

[Helferlein]

Well Mike I do not know why this solved my problem nor why this problem happened.
It was just a try like... Oh well.. let me disable the licence once and add it new.
Perhaps there was a O365 backend error while adding these users with the problem so that the license did not get replicated to all of the nodes O365 needs or whatever.
Since there are kinda no logs where you could even trace that I may not give anything more than speculations....

[Mike Resseler]

Peter, OK. Thanks for letting me know. I am going to do some testing to see if I can reproduce it. I am intrigued now

[prewest]

I am going to try the solution mentioned..
But our licenses are being management / attached via the user by a CSP provider.

[Mike Resseler]

Arnold,

Keep me informed. If that doesn't work, please log a support call. Post the case ID here and the follow-up after investigation with the engineers

[prewest]

Tried it yesterday.. just tried another backup..
unfortunately it still does not work..

I will log a support call

[prewest]

CASE ID : 03025295

[Mike Resseler]

Thanks! Keep me informed about the outcome

Cheers
Mike

[prewest]

Ok problem is fixed, this is the solution;

- In the Veeam Backup for Office 365 console navigate to Backup Infrastructure -> Backup Proxies, then right-click [VMO365] and choose Edit.
In the "Edit Backup Proxy" window click Next and specify correct credentials to connect to the proxy, for example local administrator.
Run through all the settings 'til Finish. Once you do that, your jobs should work normally.

[Mike Resseler]

Good to hear. Thanks for letting us know!

Mike

[billcouper]

I was having this issue setting up a new VBO365. When I edit the proxy server it doesn't accept any username/password, even though the proxy server is the same server the VBO365 software is running on.

I uninstalled VBO365 and reinstalled, then the backups started to run without complaining about license issues.
I edited the proxy and it still doesn't like the credentials, but it works anyway.

[Polina]

Bill,

Just to clarify first:
- do you have the proxy and the VBO server running within the same/trusted domain?
- does the option of using your current account for the proxy also not working for you?

If all of the above is true, will you please provide me your logs to investigate this with our team? Thanks!

[joelc]

This (re-adding proxy authentication) just also fixed my problem of "Failed to retrieve licenses for x users" on v3.0.0.422.

It was a standalone install and I previously haven't touched the proxy configuration.

Joel.

[Polina]

Hi Joel and welcome to the Community!

Glad that it's working for you now. Did you upgrade from v2 to v3?