Move Users From Microsoft 365 Apps for Business to Apps for Enterprise Without a License Gap
Moving users from Microsoft 365 Apps for business to enterprise by group? Add first, read licenseAssignmentStates, handle MutuallyExclusiveViolation and roll back.

This playbook covers
Table of Contents
Table of contents
To move users from Microsoft 365The KBY LexiconMicrosoft 365Microsoft 365 is Microsoft's subscription suite of Office apps and cloud services such as Exchange Online, SharePoint, OneDrive and Teams, run on an Entra ID tenant.
Apps for business to Microsoft 365 Apps for enterprise without leaving anyone unlicensed, assign the Apps for enterprise licence to a new group, add each user to that group first, confirm the new licence is applied, and only then remove them from the Apps for business group. Microsoft documents this order for moving users between licensed groups: if you remove first, the user has no licence until group-based licensing finishes processing, and an unlicensed Microsoft 365 Apps install drops into reduced functionality mode, where people can view and print but not edit. Read each user’s licenseAssignmentStates after the add. If the enterprise assignment shows MutuallyExclusiveViolation, the tenant has flagged a service plan conflict between the two products for that user, and the old licence has to go before the new one can apply. That one case has a short gap you cannot avoid, so schedule it.
#How the switch is usually handled today
Most tenants that started on Microsoft 365 Apps for business reach the enterprise edition one of two ways. The first is the automatic plan change in the Microsoft 365 admin center, which moves every user on the old plan at once and cancels the old plan. Microsoft describes it as the right choice when you want to move all users assigned to a single plan. The second is the Replace option under Users > Active users > Manage product licenses, which swaps licences for whichever users you tick.
Both work, but neither suits a tenant that licenses through groups. A replace on a user who inherits Apps for business from a group does not change the group, so the next time someone joins that group they get the old product. The all-at-once plan change gives you no pilot: if a line-of-business add-in, a shared device or a conference room PC behaves differently on the enterprise build, you find out across the whole company on the same morning. And when someone takes the shortcut of removing users from the old group and adding them to the new one in a single bulk edit, the order is wrong, and every one of them sits unlicensed until processing catches up.
#A better way: let both licences overlap, then take the old one away
The improved workflow keeps group-based licensing as the single source of truth and changes one thing: the order. A new security group carries the Apps for enterprise licence. Users join it first, the tenant applies the licence, you read the result per user, and only a clean result lets the user leave the Apps for business group.
Batches cost a little time and buy a stop point. A pilot of a few users from different teams, including whoever looks after the meeting room PCs covered in making conference room audio defaults fix themselves, tells you whether anything behaves differently before the restThe KBY LexiconRESTREST defines resource-oriented, stateless APIs built on a uniform interface; understanding its constraints clarifies scaling, caching and safe validation of state-changing calls. of the company moves.
Rendering diagram...
Two products are in play, and the service plan reference names them precisely. Microsoft 365 Apps for business appears under the string IDs O365_BUSINESS and SMB_BUSINESS, and both carry the OFFICE_BUSINESS service plan. Microsoft 365 Apps for enterprise is OFFICESUBSCRIPTION and carries a service plan of the same name. Apart from the desktop apps plan, the enterprise product includes everything the business product has (OneDrive, Office for the web, Forms and Sway) and adds Exchange Foundation, Microsoft Search, Mobile Device Management for Office 365 and Whiteboard. Microsoft says you don’t need to back up user data when you move users to a subscription with the same or more services, so this move needs no OneDrive export.
#Setting up the switch for a pilot group
You need Microsoft Entra IDThe KBY LexiconMicrosoft Entra IDA concise technical definition of Microsoft Entra ID: what it is, how it fits identity architecture, and where engineers must validate before change. P1 or a plan that includes group-based licensing, the Microsoft Graph PowerShell SDK, and enough Apps for enterprise licences for the pilot. Microsoft recommends assigning the licence 24 hours before you deploy the apps, so start the pilot well ahead of any reinstall you plan.
-
Connect with only the scopes you need.
Connect-MgGraph -Scopes "LicenseAssignment.Read.All","User.Read.All","GroupMember.ReadWrite.All". The first two cover the read-only checks; the third is the least privileged permission Graph lists for adding and removing group members. -
Check you have the licences. Run
Get-MgSubscribedSku -All | Where-Object { $_.SkuPartNumber -in 'O365_BUSINESS','SMB_BUSINESS','OFFICESUBSCRIPTION' } | Select-Object SkuPartNumber, SkuId, ConsumedUnits, @{n='Enabled';e={$_.PrepaidUnits.Enabled}}.ConsumedUnitsis the number assigned andEnabledis the number active in the subscription. Stop ifOFFICESUBSCRIPTIONdoes not have at least as many free units as the batch, because a shortfall leaves users with aCountViolation. -
Back up the old group’s membership.
Get-MgGroupMember -GroupId $businessGroupId -All | Select-Object Id | Export-Csv business-members-before.csv -NoTypeInformation. This file is your record of who to put back. -
License the new group. Create a security group for Apps for enterprise. In the Microsoft 365 admin center go to Billing > Licenses, select Assign licenses, choose the group, choose the Microsoft 365 Apps for enterprise subscription and select Assign licenses. Use a group with direct members: group-based licensing does not support nested groups, and only the first-level members of a nested group get licences. Give this group only the one product. When a group carries several products and one fails, Microsoft notes the others might not be assigned either.
-
Add a pilot user to the new group.
New-MgGroupMember -GroupId $enterpriseGroupId -DirectoryObjectId $userId. The rollback isRemove-MgGroupMemberDirectoryObjectByRef -GroupId $enterpriseGroupId -DirectoryObjectId $userId. -
Read the user’s assignment states.
Get-MgUser -UserId $userId -Property LicenseAssignmentStates | Select-Object -ExpandProperty LicenseAssignmentStates | Select-Object SkuId, AssignedByGroup, State, Error. You want a row for theOFFICESUBSCRIPTIONSKU ID withAssignedByGroupset to the new group’s ID,StateofActiveand an emptyError. The Apps for business row should still be there too. If processing hasn’t reached the user yet, wait and read again rather than moving on. -
Remove the user from the old group. Only after step 6 is clean:
Remove-MgGroupMemberDirectoryObjectByRef -GroupId $businessGroupId -DirectoryObjectId $userId. The rollback isNew-MgGroupMember -GroupId $businessGroupId -DirectoryObjectId $userId.
If step 6 shows MutuallyExclusiveViolation on the enterprise row, check that the Apps for business row is still Active, so the user is still working, and agree a time with them. Then do step 7. Once the old assignment is gone, reprocess the user in the Microsoft 365 admin center: Billing > Licenses, select Microsoft 365 Apps for enterprise, open Errors & issues, select the user and choose Reprocess. Microsoft’s fix for conflicting service plans is to disable one of the conflicting plans, remove the redundant licence or change the group assignment; removing the user from the old group is the last of those.

#Who can change licences and group membership
Assigning licences to groups needs at least the Groups Administrator, License Administrator or User Administrator role. Changing group membership is a separate right: License Administrator alone can’t add or remove members. Graph accepts the change from a group owner, a Groups Administrator or a User Administrator, among others. The tidy split is License Administrator for the person who licenses the group and ownership of the two groups for whoever moves users, or Groups Administrator for one person doing both. Keep the delegated Graph session to the three scopes above. Don’t grant Directory.ReadWrite.All for convenience: GroupMember.ReadWrite.All is the permission Graph lists for adding and removing members.
Keep the new group closed. If anyone can add members, anyone can consume Apps for enterprise licences, so the same people who control group creation (see limiting Microsoft 365 group creation to an approved security group) should own this group. If you use a Microsoft 365 group rather than a security group for licensing, check whether a Microsoft 365 group expiration policy applies to it before it carries everyone’s Office licence.
#Verify each user before you touch the next batch
The per-user check in step 6 is the main proof. Two more checks catch what it misses. In the Microsoft 365 admin center, open Billing > Licenses, select each product and look at the Errors & issues tab, which lists users with assignment problems. Group-based licensing records failures on the user object in the background, unlike a direct assignment where the error appears straight away, so this tab is where late errors show up. Then rerun the Get-MgSubscribedSku query: after a batch, ConsumedUnits for OFFICESUBSCRIPTION should rise and the Apps for business count should fall by the same number.
The assignedLicenses property on the user is not enough for this. It includes inherited licences but does not say whether a licence came from a group or was assigned directly, which is exactly what you need to know. licenseAssignmentStates does: AssignedByGroup is empty for a direct assignment and holds the group ID for an inherited one.
#What goes wrong during the move
-
The user also has a direct Apps for business licence. Removing them from the old group leaves the direct licence in place, and the enterprise row can stay in error. The
AssignedByGroupcolumn shows it. Remove the direct licence after the enterprise licence is active, or replace it in Manage product licenses. -
The enterprise row shows
CountViolation. There aren’t enough licences. Microsoft’s options are to buy more, remove unused direct assignments or free licences elsewhere. Do not remove anyone from the old group while this is showing. -
The row shows
ProhibitedInUsageLocationViolation. A service in the product isn’t available where the user is located. Set the user’s usage location correctly; users without one inherit the tenant’s location under group-based licensing. -
Someone bulk-removes the old group’s members before the new group has processed. Every one of them is unlicensed until processing completes, and their apps go into reduced functionality mode. Put them back in the old group from the CSV export.
-
The audit log shows
LicenseAssignmentAttributeConcurrencyException. Microsoft says this comes from several groups assigning the same licence at once and that it retries on its own. Don’t count the user as moved until the state readsActive.

#How to roll back one user or the whole pilot
For one user, reverse the steps in the opposite order. Add them back to the Apps for business group with New-MgGroupMember, read their assignment states until the business row is Active, and only then remove them from the Apps for enterprise group. If the business licence itself now reports MutuallyExclusiveViolation, the same scheduled gap applies in reverse: remove the enterprise membership, then reprocess the user in the Apps for business product. The reprocess button works on up to 20 users at a time.
For the whole pilot, use business-members-before.csv as the list of who belongs back in the old group, and work through it the same way. Don’t cancel or reduce the Apps for business subscription until the last batch has been checked. As long as it has licences, any user can go back.
#What to track until the old subscription is gone
Take a baseline before the pilot: the number of users in the Apps for business group, ConsumedUnits for each product, and how many users currently show any non-empty Error in licenseAssignmentStates. Three numbers then tell you whether the move is working:
- moved users whose enterprise row is
Activewith no error, which should equal the number of users moved; - users with an error on either product, which should return to the baseline after each batch;
- Apps for business
ConsumedUnits, which should reach zero when the old group is empty.
Check after every batch and once a day until the old group is empty. If any user from the latest batch is still in an error state after a reprocess, stop adding batches until you know why. The point at which you can reduce or cancel the Apps for business subscription is when its consumed count is zero and the Errors & issues tab for Apps for enterprise is empty.
#Before you switch the remaining users
- The pilot users have used the enterprise apps for long enough to hit their normal add-ins, shared mailboxes and meeting room PCs, and nobody has reported reduced functionality mode.
- Free Apps for enterprise units cover the next batch, from a fresh
Get-MgSubscribedSkurun. - The CSV backup of the Apps for business group is saved somewhere other than the admin’s laptop.
- The Apps for enterprise group has direct members only, carries one product and has a named owner.
- Users with direct Apps for business licences have been found from
AssignedByGroupand have their own plan. - Anyone expected to show
MutuallyExclusiveViolationhas an agreed time for their short gap.
When all six hold, move the next batch the same way, read every user’s state, and leave the Apps for business subscription alone until its consumed count reaches zero.
About this page
Credited to
Dates
Published
Sources
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeRelated articles
Modern Workspace & AV
Auto-Releasing Ghost-Booked Meeting Rooms Before Complaints Start
Combine Microsoft Graph webhooks and occupancy sensors to auto-decline unclaimed meeting room bookings before facilities ever raises a ticket.
Enterprise IT Management
Set a Microsoft 365 Group Naming Policy in Graph PowerShell Without Overwriting Other Group Settings
Add group name prefixes, suffixes and blocked words in Microsoft 365 with Graph PowerShell, keeping group creation and guest settings intact, with checks and rollback.
Outages
Apple Fixes Outage That Signed iPhone and Mac Users Out of iCloud and Took Down the App Store
Apple says it has resolved Tuesday's outage, which signed users out of iCloud and hit the App Store, Apple Music and Apple Pay, and blames an internal update. What to check now it is back.
Discover more
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Operate smarter, with fewer recurring tickets.
Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.
Comments
Add a thoughtful note on Move Users From Microsoft 365 Apps for Business to Apps for Enterprise Without a License Gap. Comments are checked for spam and held for moderation before appearing.