RMS Do Not Forward Option Behaviour

%3CLINGO-SUB%20id%3D%22lingo-sub-75865%22%20slang%3D%22en-US%22%3ERMS%20Do%20Not%20Forward%20Option%20Behaviour%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-75865%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20interested%20to%20know%20if%20anyone%20agrees%20with%20my%20thoughts%20around%20the%20Do%20Not%20Forward%20(DNF)%20option%20in%20Outlook%2FOWA%2C%20specifically%20whether%20it's%20possible%20to%20prevent%20users%20from%20seeing%20this%20option%20in%20Outlook%20and%20OWA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPer%20my%20understanding%2C%20the%20DNF%20option%20is%20not%20an%20RMS%20template%20but%20a%20collection%20of%20rights.%26nbsp%3B%20Therefore%2C%20I%20also%20understand%20why%20it's%20not%20possible%20to%20archive%20this%20option%20so%20users%20do%20not%20see%20it%2C%20as%20you%20can%20with%20RMS%20templates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20different%20user%20experiences%20in%20the%20Outlook%20and%20OWA%20clients.%26nbsp%3B%20In%20a%20tenant%20with%20RMS%20activated%2C%20I%20have%20a%20user%20that%20is%20not%20licensed%20and%20is%20not%20part%20of%20the%20security%20group%20to%20permit%20usage%20(via%20Set-AadrmOnboardingControlPolicy)%2C%26nbsp%3B%20When%20attempting%20to%20use%20the%20DNF%20option%20in%20Outlook%2C%20I%20get%20an%26nbsp%3Berror%20as%20the%20user%20isn't%20licensed%20and%20not%20in%20the%20correct%20security%20group.%26nbsp%3B%20However%2C%20the%20DNF%20option%20in%20OWA%20always%20works%20regardless%20of%20any%20user%20licensing%20or%20onboarding%20restrictions%2C%20as%20long%20as%20RMS%20is%20activated%20for%20Exchange%20Online%20of%20course.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExpected%20behaviour%3F%26nbsp%3B%20I%20assume%20so%2C%20but%20the%20difference%20in%20client%20experience%20is%20not%20ideal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-75865%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ERights%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76774%22%20slang%3D%22en-US%22%3ERe%3A%20RMS%20Do%20Not%20Forward%20Option%20Behaviour%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76774%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20worries%2C%20it's%20just%20that%20not%20many%20people%20bother%20with%20this%20particular%20space%20here%2C%20and%26nbsp%3Bunfortunately%20I'm%20not%20as%20knowledgeable%20with%20respect%20to%20AIP%20as%20I%20would%20like%20to%20be%20%3A)%3C%2Fimg%3E%20Getting%20an%20answer%20directly%20from%20the%20MS%20folks%20at%20the%20Yammer%20network%20is%20always%20preferred%20anyway.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76595%22%20slang%3D%22en-US%22%3ERe%3A%20RMS%20Do%20Not%20Forward%20Option%20Behaviour%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76595%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Vasil%2C%20I%20was%20looking%20at%20that%20in%20parallel%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-75966%22%20slang%3D%22en-US%22%3ERe%3A%20RMS%20Do%20Not%20Forward%20Option%20Behaviour%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-75966%22%20slang%3D%22en-US%22%3E%3CP%3EI%20suggest%20to%20ask%20this%20question%20in%20the%20AIP%20Yammer%20network%2C%20where%20all%20the%20MS%20folks%20lurk.%20Here's%20the%20address%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Faskipteam%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.yammer.com%2Faskipteam%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I'm interested to know if anyone agrees with my thoughts around the Do Not Forward (DNF) option in Outlook/OWA, specifically whether it's possible to prevent users from seeing this option in Outlook and OWA.

 

Per my understanding, the DNF option is not an RMS template but a collection of rights.  Therefore, I also understand why it's not possible to archive this option so users do not see it, as you can with RMS templates.

 

I see different user experiences in the Outlook and OWA clients.  In a tenant with RMS activated, I have a user that is not licensed and is not part of the security group to permit usage (via Set-AadrmOnboardingControlPolicy),  When attempting to use the DNF option in Outlook, I get an error as the user isn't licensed and not in the correct security group.  However, the DNF option in OWA always works regardless of any user licensing or onboarding restrictions, as long as RMS is activated for Exchange Online of course.

 

Expected behaviour?  I assume so, but the difference in client experience is not ideal.

3 Replies

I suggest to ask this question in the AIP Yammer network, where all the MS folks lurk. Here's the address: https://www.yammer.com/askipteam/

Thanks Vasil, I was looking at that in parallel too.

No worries, it's just that not many people bother with this particular space here, and unfortunately I'm not as knowledgeable with respect to AIP as I would like to be :) Getting an answer directly from the MS folks at the Yammer network is always preferred anyway.