-
- Enthusiast
- Posts: 32
- Liked: 4 times
- Joined: Nov 08, 2019 4:32 pm
- Full Name: James Hurrell
- Contact:
Mailbox converted from "user" to "shared" - best way to remove license?
I have a user mailbox that has recently been converted to a "shared" mailbox. This user has no associated OneDrive data, but it is using up one VBO license. I would like to continue backing up the shared mailbox, but obviously I'd like to free up the VBO license.
My understanding is that you can't remove a license if the repository still contains user data, so my guess is that I should first remove the data from the repo, then remove the license using the Powershell command and finally just let it resynchronise in the next scheduled job... Can anyone confirm if this is the right way to approach this or is there a better way?
thanks.
My understanding is that you can't remove a license if the repository still contains user data, so my guess is that I should first remove the data from the repo, then remove the license using the Powershell command and finally just let it resynchronise in the next scheduled job... Can anyone confirm if this is the right way to approach this or is there a better way?
thanks.
-
- Product Manager
- Posts: 10277
- Liked: 2746 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
If you wait for 31 days, the license should be automatically revoked. Hopefully Veeam has integrated such logic when changing a user mailbox to shared mailbox.
If you can wait, then i recommend to wait.
If not, then you need to remove all the user data first before revoking the license. There is no better way.
If the license is not revoked after 31 days, open a support case and ask for assistance why it is not happening automatically.
If you can wait, then i recommend to wait.
If not, then you need to remove all the user data first before revoking the license. There is no better way.
If the license is not revoked after 31 days, open a support case and ask for assistance why it is not happening automatically.
Product Management Analyst @ Veeam Software
-
- Enthusiast
- Posts: 32
- Liked: 4 times
- Joined: Nov 08, 2019 4:32 pm
- Full Name: James Hurrell
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
Thanks Fabian! I can wait, so i'll let it run its course.
-
- Product Manager
- Posts: 10277
- Liked: 2746 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
No problem, James 

Product Management Analyst @ Veeam Software
-
- Product Manager
- Posts: 8220
- Liked: 1333 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
Mildur is correct. After 31 days the license will be freed. However, once you add this shared mailbox, it need to be completely unlicensed in M365 also or we will continue to see it as a paid account.
-
- Enthusiast
- Posts: 32
- Liked: 4 times
- Joined: Nov 08, 2019 4:32 pm
- Full Name: James Hurrell
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
Thanks Mike. Yes, the license has been removed in M365 on this mailbox. I'll keep an eye on it.
-
- Veeam Software
- Posts: 180
- Liked: 22 times
- Joined: Mar 05, 2018 3:10 pm
- Full Name: Tobias Gietz
- Location: Germany
- Contact:
Re: Mailbox converted from "user" to "shared" - best way to remove license?
Hi,
after converting the mailbox to a shared one. Is then a new full backup necessary or job modifications?
Best regards
Tobias
after converting the mailbox to a shared one. Is then a new full backup necessary or job modifications?
Best regards
Tobias
-
- Veeam Software
- Posts: 3456
- Liked: 828 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
Re: Mailbox converted from "user" to "shared" - best way to remove license?
Hi Tobias,
Backups will continue, no further modifications are needed. Note though, that in older restore points it will also be displayed as Shared; i.e. once the type is changed and backed up, it is applied to all restore points, including historical.
Thanks!
Backups will continue, no further modifications are needed. Note though, that in older restore points it will also be displayed as Shared; i.e. once the type is changed and backed up, it is applied to all restore points, including historical.
Thanks!
Who is online
Users browsing this forum: Semrush [Bot] and 11 guests