SOLVED

M365 Customer Lockbox licensing

%3CLINGO-SUB%20id%3D%22lingo-sub-1480182%22%20slang%3D%22en-US%22%3EM365%20Customer%20Lockbox%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480182%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20someone%20explain%20us%20how%20customer%20lockbox%20works%20under%20mixed%20licensing%3F%20For%20example%3A%20We%20have%2099%20M365%20E3%20licences%20and%20one%20M365%20E5%20license.%20In%20this%20situation%20there%20will%20be%20only%20one%20user%2Fadmin%20(which%20have%20M365%20E5%20license)%20able%20to%20turn%20on%20and%20off%20lockbox%20feature%20and%20also%20approve%20requests%3F%20Others%20users%20with%20E3%20licence%20can%C2%B4t%20turn%20lockbox%20feature%20on%20or%20off%20or%20approve%20requests%20despite%20they%20are%20global%20admins%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1480182%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480316%22%20slang%3D%22en-US%22%3ERe%3A%20M365%20Customer%20Lockbox%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480316%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F706374%22%20target%3D%22_blank%22%3E%40Mi1anovic%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETake%20a%20look%20at%20this%20-%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fitblog.ldlnet.net%2Fwp-content%2Fuploads%2F2019%2F06%2FGuide-to-MS-O365-Licensing.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fitblog.ldlnet.net%2Fwp-content%2Fuploads%2F2019%2F06%2FGuide-to-MS-O365-Licensing.pdf%3C%2FA%3E%26nbsp%3B-%20it%20explains%20the%20tenant%20level%20feature%20guidance%20in%20relation%20to%20licensing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGlobal%20Administrators%20and%20Customer%20Lockbox%20Access%20Approvers%20can%20approve%20Customer%20Lockbox%20access%20requests%20from%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETenant%20level%20services%20can%20be%20very%20tricky%20when%20it%20comes%20to%20licensing.%26nbsp%3B%20By%20the%20letter%20of%20the%20law%2C%20you%20probably%20should%20have%20an%20M365%20E5%20licence%20for%20every%20user%20in%20your%20tenant%20if%20you%20are%20using%20this%20feature.%26nbsp%3B%20It%20will%20work%20if%20you%20only%20have%20one%20though.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20very%20dangerous%20grey%20area%20in%20my%20opinion.%26nbsp%3B%20Same%20issue%20occurs%20with%20the%20features%20of%20O365%20ATP.%26nbsp%3B%20They%20are%20activated%20at%20a%20tenant%20level%2C%20but%20all%20users%20should%20be%20appropriately%20licensed%20to%20benefit%20from%20the%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480327%22%20slang%3D%22en-US%22%3ERe%3A%20M365%20Customer%20Lockbox%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480327%22%20slang%3D%22en-US%22%3EOkay%20I%20got%20it.%20This%20is%20same%20situation%20as%20Premium%20AAD%20licenses.%20If%20AAD%20is%20Azure%20AD%20for%20Office%20365%20and%20we%20want%20to%20AAD%20Premium%20we%20need%20buy%20at%20least%20one%20license%20for%20user%2Fadmin%20but%20others%20users%20will%20not%20be%20able%20benefit%20from%20that.%20We%20will%20need%20premium%20aad%20licence%20for%20every%20user.%20So%20this%20lockbox%20feature%20is%20working%20on%20same%20license%20idea%20as%20AAD%20premium%20right%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480453%22%20slang%3D%22en-US%22%3ERe%3A%20M365%20Customer%20Lockbox%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480453%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F622573%22%20target%3D%22_blank%22%3E%40Milan30%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20that's%20correct.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480456%22%20slang%3D%22en-US%22%3ERe%3A%20M365%20Customer%20Lockbox%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480456%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3BThank%20you.%20You%20helped%20me%20a%20lot.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

Can someone explain us how customer lockbox works under mixed licensing? For example: We have 99 M365 E3 licences and one M365 E5 license. In this situation there will be only one user/admin (which have M365 E5 license) able to turn on and off lockbox feature and also approve requests? Others users with E3 licence can´t turn lockbox feature on or off or approve requests despite they are global admins?

4 Replies
best response confirmed by Mi1anovic (Senior Member)
Solution

@Mi1anovic 

 

Take a look at this -  https://itblog.ldlnet.net/wp-content/uploads/2019/06/Guide-to-MS-O365-Licensing.pdf - it explains the tenant level feature guidance in relation to licensing.

 

Global Administrators and Customer Lockbox Access Approvers can approve Customer Lockbox access requests from Microsoft.

 

Tenant level services can be very tricky when it comes to licensing.  By the letter of the law, you probably should have an M365 E5 licence for every user in your tenant if you are using this feature.  It will work if you only have one though.  

 

A very dangerous grey area in my opinion.  Same issue occurs with the features of O365 ATP.  They are activated at a tenant level, but all users should be appropriately licensed to benefit from the features.

Okay I got it. This is same situation as Premium AAD licenses. If AAD is Azure AD for Office 365 and we want to AAD Premium we need buy at least one license for user/admin but others users will not be able benefit from that. We will need premium aad licence for every user. So this lockbox feature is working on same license idea as AAD premium right?

@Milan30 

 

Yes that's correct.

@PeterRising Thank you. You helped me a lot.