Set-MSOLUserLicenseOptions Should Use -EnabledPlans Rather Than -DisabledPlans
When automating user licensing, setting which service plans are disabled rather than enabled is backward and risky. Case in point: when new licenseable service plans are added to a SKU (e.g. Yammer), they won't be taken into account in any existing automation scripts. The end result will be that users will automatically receive any newly added service plans.
A better approach would be to set plans which are to be enabled, which makes the entitlements much more explicit.
See my comment on this item:
I agree, have had such a difficult time with enabling and disabling services/plans. disabled plans is impossible to maintain (at least without a wildcard- which I have yet to see an example of ). Enabled plans really needs to exist, I've suggested the same thing.
Jared Pickerell - Troy Public Schools commented
Yes, this would be fantastic!!!! Such a pain to have to explicitly exclude services that we don't want to assign.