License Reconciliation Needed

ComputerHabit 636 Reputation points

What does LicenseReconciliationNeeded do and how do I fix it?

$msoUsers = Get-MSOLUser -All | where {$_.LicenseReconciliationNeeded -eq $true }

I've struggled with this for a long time. I opened a case with support and they don't know how it comes about or how to resolve them.

Could anybody go into detail on what an admin should be doing with this attribute?

Office Management
Office Management
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Management: The act or process of organizing, handling, directing or controlling something.
1,778 questions
Microsoft Exchange Online Management
Microsoft Exchange Online Management
Microsoft Exchange Online: A Microsoft email and calendaring hosted service.Management: The act or process of organizing, handling, directing or controlling something.
3,683 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vasil Michev 79,301 Reputation points MVP

    As taken from the official documentation:

    LicenseReconciliationNeeded. Whether or not the user currently has a mailbox without a license. In this case, the user should be licensed with 30 days to avoid losing their mailbox.

    You fix it by assigning a license that includes Exchange Online plan, or by converting the mailbox to shared one (as long as its size is lower than 50GB and no archive is provisioned).

1 additional answer

Sort by: Most helpful
  1. ComputerHabit 636 Reputation points

    Ah that's probably it. We hold everything with retention policies.

    Now I'm guessing these mailboxes are just kind of stuck at the moment. I had some issues with automation early on when learning what's required. I had a few mailboxes get unlicensed before an attempt to convert to shared.

    I've also had them show up in the MSOL errors list which I did clear. I just need to take these out of the policy for a little bit.

    Thanks for that.

    0 comments No comments