Product Feedback for Advanced Message Encryption

%3CLINGO-SUB%20id%3D%22lingo-sub-2998973%22%20slang%3D%22en-US%22%3EProduct%20Feedback%20for%20Advanced%20Message%20Encryption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2998973%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%20I've%20just%20evaluated%26nbsp%3B%3CEM%3EAdvanced%20Message%20Encryption%3C%2FEM%3E%20for%20Exchange%20Online%26nbsp%3B%20so%20thought%20I%20would%20feedback%20my%20thoughts.%20It's%20a%20good%20product%20if%20your%20only%20goal%20is%20to%20guarantee%20that%20emails%20are%20encrypted.%20However%20if%20your%20goal%20is%20to%20limit%20data%20breaches%2C%20there%20are%20two%20minor%20features%20missing%20which%20significantly%20limit%20its%20usefulness%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EIt's%20not%20possible%20to%20revoke%20encrypted%20emails*%20sent%20to%20Microsoft%20tenanted%20email%20accounts%20(basically%20almost%20everyone)%2C%20since%20they%20are%20displayed%20inline%20in%20Outlook%20clients%2C%20rather%20than%20using%20a%20link-based%20experience%20(where%20the%20recipient%20is%20required%20to%20sign%20in%20to%20the%20OME%20portal%20to%20view%20the%20message).%20%3CFONT%20size%3D%222%22%3E%26nbsp%3B*This%20applies%20to%20emails%20encrypted%20In%20Outlook%20by%20selecting%20the%20%3CEM%3EEncrypt%3C%2FEM%3E%20drop%20down%20menu%2C%20or%20by%20applying%20a%20Sensitivity%20Label.%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EIt's%20not%20possible%20for%20the%20user%20(or%20an%20admin)%20to%20query%20whether%20a%20sent%20link-based%20encrypted%20email%20has%20been%20read%20or%20not%20by%20the%20recipient%2C%20and%20if%20so%20at%20what%20date%20and%20time.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20two%20features%20are%20likely%20easy%20to%20implement%2C%20and%20would%20make%20this%20product%20much%20more%20useful.%20End%20users%20would%20be%20able%20to%20rectify%20their%20own%20accidental%20email%20data%20breaches%2C%20for%20example%20forgetting%20to%20use%20the%20BCC%20field%2C%20or%20fat-fingering%20the%20Outlook%20%3CEM%3ETo%3C%2FEM%3E%20field%20autocomplete%20and%20selecting%20the%20wrong%20recipient.%20I%20understand%20that%20products%20such%20as%20%3CEM%3EMimecast%3C%2FEM%3E%20and%20%3CEM%3EEgress%20Protect%3C%2FEM%3E%20already%20have%20these%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeing%20able%20to%20reliably%20revoke%20an%20email%2C%20and%20know%20for%20sure%20whether%20it%20was%20accessed%20or%20not%20by%20the%20recipient%20(and%20prove%20so)%2C%20is%20the%20difference%20between%20being%20legally%20required%20to%20report%20a%20breach%20to%20your%20region's%20data%20regulator%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20that%20some%20organisations%20may%20have%20the%20priority%20of%20an%20easy%20user%20experience%2C%20so%20would%20want%20to%20keep%20the%20encrypted%20message%20inline%20in%20Outlook%2C%26nbsp%3Bbut%20for%20those%20whose%20priority%20is%20data%20breach%20minimisation%2C%20being%20able%20to%20switch%20this%20off%20and%20use%20the%20link-based%20experience%20for%20all%20recipients%20would%20be%20very%20useful.%20I%20understand%20that%20it's%20possible%20to%20setup%20a%20transport%20rule%20to%20force%20recipients%20to%20use%20the%20OME%20portal%2C%20but%20this%20only%20works%20if%20you%20encrypt%20*all*%20of%20your%20organisation's%20messages%2C%20rather%20than%20those%20the%20user%20has%20selected%20to%20encrypt.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20feature%20became%20available%20I%20would%20have%20no%20hesitation%20to%20roll%20it%20out%20organisation-wide.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2998973%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdvanced%20Message%20Encryption%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EInline%20Experience%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELink-Based%20Experience%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20Message%20Encryption%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOME%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3000721%22%20slang%3D%22en-US%22%3ERe%3A%20Product%20Feedback%20for%20Advanced%20Message%20Encryption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3000721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1227878%22%20target%3D%22_blank%22%3E%40mikedoneghan%3C%2FA%3E%26nbsp%3BHello%2C%20just%20gonna%20add%20my%20two%20cents.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOffice%20Message%20Encryption%20is%20a%20great%20built-in%20encryption%20tool%20for%20%3CEM%3Eemails%3C%2FEM%3E%20with%20the%20options%20Encrypt-only%20and%20Do%20Not%20Forward.%20That's%20kind%20of%20what%20you%20can%20do%20with%2C%20and%20only%20use%20the%20default%20OME%20template.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20I%20haven't%20worked%20with%20Advanced%20OME%20but%20here%20you%20have%20more%20possibilities%20with%20branding%2Ftemplates.%20You%20can%20use%20multiple%20and%20specify%20more%20granular%20options%2C%20and%20not%20all%20email%20have%20to%20be%20encrypted.%20I%20assume%20you've%20looked%20in%20the%20EXO%20admin%20center%20and%20played%20around%20with%20possible%20scenarios%20as%20which%20custom%20branding%20template%20to%20use%20and%20apply%20O365%20Message%20Encryption%20or%20not%3F%20And%20as%20you%20mention%2C%20you%20can%20revoke%20access%20in%20some%20scenarios.%20But%20when%20you%20use%20custom%20branding%20you're%20using%20the%20wrapper%20all%20the%20time%2C%20hence%20more%20secure%20as%20the%20recipient%20needs%20to%20access%20to%20OME%20portal%20and%20then%20you%20have%20the%20possibility%20to%20revoke%20access%20and%20set%20expiration%20date.%20Bear%20in%20mind%20that%20revoke%20and%20recall%20are%20different%20things.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20docs%20have%20several%20articles%20about%20OME%20and%20Advanced%20OME%2C%20perhaps%20you've%20already%20browsed%20through%20them%20but%20I%20recommend%20you%20go%20there%20and%20have%20look.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20use%20a%20%3CSTRONG%3Emore%20secure%20and%20governance%3C%2FSTRONG%3E%20approach%20you%20shouldn't%20look%20at%20OME%20really.%20But%20instead%20DLP%20and%20sensitivity%20labels.%20You%20can%20revoke%20with%20the%20latter%20if%20using%20the%20unified%20client.%20As%20an%20admin%20you%20always%20have%20the%20possibility.%20For%20these%20two%20tools%20you%20also%20have%20the%20audit%20log%20where%20you%20can%20find%20things%20like%26nbsp%3B%3CEM%3ESensitivityLabeledFileOpened%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3000887%22%20slang%3D%22en-US%22%3ERe%3A%20Product%20Feedback%20for%20Advanced%20Message%20Encryption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3000887%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F588790%22%20target%3D%22_blank%22%3E%40ChristianJBergstrom%3C%2FA%3E%26nbsp%3BMany%20thanks%20for%20your%20response.%20I've%26nbsp%3B%3CSPAN%3Eplayed%20around%20with%20Advanced%20Message%20Encryption%20custom%20branding%20templates%2C%20and%20it%20seems%20that%20the%20%3CEM%3EDo%20not%20Forward%3C%2FEM%3E%20and%20%3CEM%3EEncrypt%3C%2FEM%3E%20options%20only%20use%20the%20standard%20OME%20template%2C%20so%20you%20can't%20force%20a%20link-based%20experience%20with%20these.%20However%20it%20is%20possible%20to%20create%20a%20rule%20to%20use%20a%20custom%20template%20which%20forces%20a%20link-based%20experience%2C%20but%20this%20only%20works%20if%20the%20transport%20rule%20is%20for%20all%20emails%20sent%20in%20the%20organisation%20are%20to%20be%20encrypted%2C%20which%20we%20don't%20want.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-365%2Fforce-external-users-to-use-ome-portal-versus-decryption-in%2Fm-p%2F1668579%22%20target%3D%22_self%22%3EThis%20Tech%20Community%20article%3C%2FA%3E%20sheds%20some%20light%20on%20this.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20mentioned%20using%20DLP%20and%20sensitivity%20labels%2C%20however%20I%20have%20already%20setup%20a%20sensitivity%20label%20and%20get%20the%20same%20behaviour%20as%20if%20the%20%3CEM%3EEncrypt%3C%2FEM%3E%20option%20were%20used%2C%20i.e.%20it%20only%20uses%20a%20link-based%20experience%20if%20all%20emails%20are%20encrypted%20by%20a%20transport%20rule%2C%20and%20not%20selectively%20based%20on%20the%20sensitivity%20label%20being%20used.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you've%20managed%20to%20implement%20sensitivity%20label(s)%20which%20allows%20a%20link-based%20experience%20(thus%20allowing%20revocable%20emails)%20for%20*all*%20(including%20Office%20365%20%2F%20Outlook.com)%20recipients%2C%20and%20which%20doesn't%20force%20every%20email%20to%20be%20encrypted%2C%20then%20I'd%20be%20interested%20to%20hear%20how%20you've%20achieved%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20mentioned%20the%20unified%20client%2C%20I%20had%20to%20look%20that%20up.%20I%20read%20that%20Microsoft%20are%20planning%20on%20deprecating%20Office%20Apps%20and%20using%20only%20OWA.%20So%20are%20you%20referring%20to%20OWA%20being%20the%20unified%20client%3F%20If%20so%20I%20think%20you%20can%20only%20revoke%20emails%20using%20OWA%20anyway.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ERegarding%26nbsp%3B%3CEM%3ESensitivityLabeledFileOpened%3C%2FEM%3E%2C%20is%20this%20a%20variable%20to%20detail%20whether%20an%20email%20has%20been%20read%2C%20or%20is%20it%20only%20for%20an%20attached%20file%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi there, I've just evaluated Advanced Message Encryption for Exchange Online  so thought I would feedback my thoughts. It's a good product if your only goal is to guarantee that emails are encrypted. However if your goal is to limit data breaches, there are two minor features missing which significantly limit its usefulness:-

 

  • It's not possible to revoke encrypted emails* sent to Microsoft tenanted email accounts (basically almost everyone), since they are displayed inline in Outlook clients, rather than using a link-based experience (where the recipient is required to sign in to the OME portal to view the message).  *This applies to emails encrypted In Outlook by selecting the Encrypt drop down menu, or by applying a Sensitivity Label.

 

  • It's not possible for the user (or an admin) to query whether a sent link-based encrypted email has been read or not by the recipient, and if so at what date and time.

 

These two features are likely easy to implement, and would make this product much more useful. End users would be able to rectify their own accidental email data breaches, for example forgetting to use the BCC field, or fat-fingering the Outlook To field autocomplete and selecting the wrong recipient. I understand that products such as Mimecast and Egress Protect already have these features.

 

Being able to reliably revoke an email, and know for sure whether it was accessed or not by the recipient (and prove so), is the difference between being legally required to report a breach to your region's data regulator or not.

 

I understand that some organisations may have the priority of an easy user experience, so would want to keep the encrypted message inline in Outlook, but for those whose priority is data breach minimisation, being able to switch this off and use the link-based experience for all recipients would be very useful. I understand that it's possible to setup a transport rule to force recipients to use the OME portal, but this only works if you encrypt *all* of your organisation's messages, rather than those the user has selected to encrypt.

 

If this feature became available I would have no hesitation to roll it out organisation-wide.

6 Replies

@mikedoneghan Hello, just gonna add my two cents.

 

Office Message Encryption is a great built-in encryption tool for emails with the options Encrypt-only and Do Not Forward. That's kind of what you can do with, and only use the default OME template.

 

Now I haven't worked with Advanced OME but here you have more possibilities with branding/templates. You can use multiple and specify more granular options, and not all email have to be encrypted. I assume you've looked in the EXO admin center and played around with possible scenarios as which custom branding template to use and apply O365 Message Encryption or not? And as you mention, you can revoke access in some scenarios. But when you use custom branding you're using the wrapper all the time, hence more secure as the recipient needs to access to OME portal and then you have the possibility to revoke access and set expiration date. Bear in mind that revoke and recall are different things.

 

The docs have several articles about OME and Advanced OME, perhaps you've already browsed through them but I recommend you go there and have look.

 

If you want to use a more secure and governance approach you shouldn't look at OME really. But instead DLP and sensitivity labels. You can revoke with the latter if using the unified client. As an admin you always have the possibility. For these two tools you also have the audit log where you can find things like SensitivityLabeledFileOpened

@ChristianJBergstrom Many thanks for your response. I've played around with Advanced Message Encryption custom branding templates, and it seems that the Do not Forward and Encrypt options only use the standard OME template, so you can't force a link-based experience with these. However it is possible to create a rule to use a custom template which forces a link-based experience, but this only works if the transport rule is for all emails sent in the organisation are to be encrypted, which we don't want. This Tech Community article sheds some light on this.

 

You mentioned using DLP and sensitivity labels, however I have already setup a sensitivity label and get the same behaviour as if the Encrypt option were used, i.e. it only uses a link-based experience if all emails are encrypted by a transport rule, and not selectively based on the sensitivity label being used.

 

If you've managed to implement sensitivity label(s) which allows a link-based experience (thus allowing revocable emails) for *all* (including Office 365 / Outlook.com) recipients, and which doesn't force every email to be encrypted, then I'd be interested to hear how you've achieved that.

 

You mentioned the unified client, I had to look that up. I read that Microsoft are planning on deprecating Office Apps and using only OWA. So are you referring to OWA being the unified client? If so I think you can only revoke emails using OWA anyway. 


Regarding SensitivityLabeledFileOpened, is this a variable to detail whether an email has been read, or is it only for an attached file?

 

 

@mikedoneghan Wow, many questions. You know I have a day job right? ;) As with the previous conversation from a year ago, which you linked to, I believe I did some deeper testing and ended with a reply from my OME findings (my old account).

 

Just to give you an example.

 

I used this right now and the wrapper showed up in my Outlook client (M365 desktop app). As I don't have Advanced OME I cannot use other branding than default OME Configuration. You on the other hand can choose multiple (if created) by clicking on the OME Config link, and the Encrypt link, and add other conditions and combine them.

 

ChristianJBergstrom_0-1637752783485.png

 

If using sensitivity labels you don't have to go here. Those were previously named AIP labels/templates. OME is simply a small part of "AIP" using the rights management feature for the email/attachment. Sensitivity labels are all data everywhere, not only email.

 

You should instead work with your organization so the business classifies your data and from those results IT sets up sensitivity labels and label policies which you publish to your users apps, configuring permissions for them or letting them decide themselves, enforce in Outlook or Office apps (Word, PowerPoint, Excel). Add Data Loss Prevention where you have so many settings which can even prevent your users from accidentally send emails or documents to the wrong recipient using policy tips and policy notifications.

 

I meant the downloadable "AIP" unified labeling client. And I haven't heard a thing about discontinuing M365 apps.

 

As for you final question perhaps this will answer it How to Report Audit Events Generated for Sensitivity Labels - Office 365 for IT Pros (office365itpro... 

 

@ChristianJBergstrom Thanks for your support! I have been tasked with setting up sensitivity labels and policies for our organisation in Office 365, with a view to using them in Outlook, as well as for all files in SharePoint as well. However note that I also tested the transport rule you quoted using a sensitivity label (applied from within OWA), and I'm stuck with the same problem of it encrypting all sent emails (with a link-based experience) rather than only those with the sensitivity label applied.

 

I've been trying to get the Unified Labeling Client you mentioned working so I can try this from the Outlook app (in case it has a different behaviour which does what I want, i.e. display a link-based experience for only each email sent using a sensitivity label),  but I could do with a hand as no labels are showing. 

 

I've created a label:-

mikedoneghan_0-1637939438952.png

And also created a policy to publish the label to myself (without any policy settings though as I don't want to force anything yet) :-

 

mikedoneghan_1-1637939551540.png

 

Also here are my licenses:-

mikedoneghan_2-1637939827703.png

 

However no labels are showing in the Unified Labelling Client:-

mikedoneghan_3-1637939877243.png

 

But the sensitivity label does show in OWA though:-

mikedoneghan_4-1637939922797.png

 

Am I missing a step here? The Unified Labelling Client admin guide doesn't to mention anything else which needs doing. There doesn't seem to be any other way to configure it.

 

All the best,

 

Mike

 

 

 

Hello! I honestly think it’s better if you ask for assistance using the official support. Not my intention if that sounds impolite in any way. It’s just too complex and time consuming as a community member.
Will do, many thanks.