Office Message Encryption - Branding

[Cache]

Hi all

 

Has anyone been able to successfully apply branding to the OME through Office 365? I've followed the steps in this article however out of the ones I set, the only branding that has applied successfully seems to be the school logo on the OME portal: https://support.office.com/en-gb/article/add-your-organization-s-brand-to-your-encrypted-messages-7a29260d-2959-42aa-8916-feceff6ee51d

 

Just wondered if there is an extra step somewhere that isn't detailed that I'm missing.

 

Thanks

[Domino]

Mine works okay, and I used the same guide

 

 

if you run "get-omeconfiguration -Identity "OME Configuration" does it return your expected settings?

[Cache]

Yes, get-omeconfiguration returns what I've set, but doesn't apply the logo to the email and doesn't include the Email Text I've added in. It does apply the logo to the OME Portal though which is what I don't get.

[jonnykewell1]

@themightymrp tested this with me and it only showed up on a non Office 365 system. Do you have a gmail account you can test it with?

[Cache]

Yeah I keep emailing my gmail account to rule out it not applying to anything internal.

 

 

[themightymrp]

I used the commands from this page:

 

https://support.office.com/en-us/article/add-your-organization-s-brand-to-your-encrypted-messages-7a29260d-2959-42aa-8916-feceff6ee51d?ui=en-US&rs=en-US&ad=US

 

And ended up with something like this (not a final draft of text). The colour scheme matches in with our website branding.

 

[themightymrp]

Had a thought yesterday. We use our photocopiers sometimes to scan and email documents. I'm going to set a rule that catches anything from photocopiers@ email address and adds encryption to it. Just to cover my back!

[HereIGoAgain2601]

Hi,

 

I must be doing something stupid as just getting an error that the cmdlet is not recognised. I've imported the Exchange powershell commands is this the right set?

[themightymrp]

Hmmm strange, I'm getting that same problem when I try it now?? Worked fine when I did it the other week. Yes it was just the standard exchange powershell commands. It now says command isn't recognised??

[HereIGoAgain2601]

Glad it's not just me! Thought I was losing it!

[Cache]

I used the commands from this page:

 

https://support.office.com/en-us/article/add-your-organization-s-brand-to-your-encrypted-messages-7a29260d-2959-42aa-8916-feceff6ee51d?ui=en-US&rs=en-US&ad=US

 

And ended up with something like this (not a final draft of text). The colour scheme matches in with our website branding.

 

[ATTACH=CONFIG]49237[/ATTACH]

 

Yep, that's the same page I linked above - could you post your get-omeconfiguration output so I can try and see if there's any differences to mine that I can force?

 

I might try setting a colour and see if it is something as obvious as that....

 

I did have issues with the get/set commands yesterday, I switched my powershell link from the one on the page to one that's written in my notes (not a major difference, but can't remember the exact difference) and the command worked everytime after that.

[themightymrp]

Sorry in the delay in replying to this. I'm still unable to run the Get-OMEConfiguration command Or any of the OME commands by the look of it. Not sure why, I'm connecting using the same methods I always use and all other O365 cmdlets are working fine

[Mako]

Le Reddit. Looks like they've removed the cmdlet, either temporarily or permanently but there's no documentation from Microsoft on it.

[RobFuller]

I was having issues until I tried opening PowerShell via the Windows Azure Active Directory Module for Windows PowerShell window, worked fine only yesterday.

 

Normal Powershell doesn't load the cmdlet for some reason.

[themightymrp]

Well, with no changes to my settings whatsoever, the Get-OMEConfiguration and Set-OMEConfiguration commands have started working again?!

 

As request by @Cache above, here is a screenshot of my config, plus at the top you will see the contents of the quicky powershell scripts I use for connecting.

 

[leegcvcc]

Is there not a difference between using "Protect" from OWA and using a Rule to Encrypt? I get different messages so assume there is. Maybe that's the issue?

[Cache]

Well, with no changes to my settings whatsoever, the Get-OMEConfiguration and Set-OMEConfiguration commands have started working again?!

 

As request by @Cache above, here is a screenshot of my config, plus at the top you will see the contents of the quicky powershell scripts I use for connecting.

 

[ATTACH=CONFIG]49346[/ATTACH]

 

Interesting - the state on yours says Changed, where as mine says unchanged....

[Cache]

Ok, after setting various additional options such as background colour I gave up, removed all the branding and reconfigured it and the thing decided to work straight away!

 

So the problem, whatever it was, is now solved!

[DrCheese]

I had to log a support call with Microsoft before any of this worked - I didn't even have the Get-OME bit working (It said cmdlet not found) - The engineer forced an update on our tenant overnight and it eventually kicked through the following day.