SOLVED

Applying an eDiscovery hold to an E1 licence

Steel Contributor

The link below describes the Security and Compliance Center availability for Business and Enterprise Plans:

 

https://technet.microsoft.com/en-us/library/dn933793.aspx

 

Next to the features 'eDiscovery export' and 'eDiscovery Holds (including query based eDiscovery holds)' it has 'No' under the Office 365 Enterprise E1 column. Some of our admins believe that this prevents us from applying an eDiscovery hold to an E1 licence.

 

However, we can add an E1 user to a case in the eDiscovery section of the Search and Investigation part of the Security and Compliance Center.

 

Can anyone explain why E1 has a 'No' next to it in the page above but we can add an E1 to an eDiscovery case?

Thank you

1 Reply
best response confirmed by Max Fritz (Iron Contributor)
Solution
As in the article you linked, a minimum of E3 licensing (or addon licensing with E1) is needed for certain eDiscovery and Hold features (exports and holds mainly).

There is no actual limitation (today at least) in the interface that stops you from using those features for a user without the proper license. However, you would be out of compliance if you were to use those features on a user without the right licensing. Microsoft at any time could choose to audit that.

Simply put, Microsoft trusts you to use the feature according to your licensing agreement. I'd recommend sticking to that. If you find your organization needs export and hold features, you can get addon licensing to enhance your E1 licenses, or consider E3/E5 licenses.

Hope that helps!
1 best response

Accepted Solutions
best response confirmed by Max Fritz (Iron Contributor)
Solution
As in the article you linked, a minimum of E3 licensing (or addon licensing with E1) is needed for certain eDiscovery and Hold features (exports and holds mainly).

There is no actual limitation (today at least) in the interface that stops you from using those features for a user without the proper license. However, you would be out of compliance if you were to use those features on a user without the right licensing. Microsoft at any time could choose to audit that.

Simply put, Microsoft trusts you to use the feature according to your licensing agreement. I'd recommend sticking to that. If you find your organization needs export and hold features, you can get addon licensing to enhance your E1 licenses, or consider E3/E5 licenses.

Hope that helps!

View solution in original post