Email Signatures - OWA Issue

[ZakFarnworth]

Hi all,

 

Microsoft have recently upgraded Outlook Web App for all tenants I believe. I have been using a set email signatures script for nearly a year. Since Microsoft have upgraded their servers, The set-Mailboxconfiguration -SignatureHTML cmdlet no longer works. I have tried absolutely everything to find a work-around but no luck so far except pay companies like CodeTwo. I have been using this email signature script on my personal tenant for testing.

Just wondering if anyone knows a FREE service that allows me to set Email Signatures. I know exchange online can set disclaimers but this isn't something I am supportive on implementing as I like to see the email signature set when composing the message. I've tried MS Graph but that doesn't have the functionality to set email signatures.

 

Thanks,

Zak

[Simcfc73]

Be interested in this too. I've implemented Disclaimers which works ok...

[ZakFarnworth]

Yeah, it seems to be a worldwide issue with every Microsoft 365 tenant. Extremely annoying!

[ZakFarnworth]

Be interested in this too. I've implemented Disclaimers which works ok...

 

Upon browsing some Microsoft documentation, I came across this...

 

Microsoft have enabled roaming signatures for all organisations I remember hearing about so this may be something that if seriously affected by, we need to have a ticket open.

[h=3]-SignatureHtml[/h]

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

The SignatureHtml parameter specifies the email signature that's available to the user in HTML-formatted messages in Outlook on the web. You can use plain text or text with HTML tags. However, any JavaScript code is removed.

To automatically add this email signature to HTML-formatted messages created by the user in Outlook on the web, the AutoAddSignature parameter must be set to $true.

[tdk1069]

I did that - opened a support ticket to get it disabled and my script carried on working as normal - for now... Unsure if it will become an issue later down the line or not but thats for later down the line

[Sadiq_to222]

I did that - opened a support ticket to get it disabled and my script carried on working as normal - for now... Unsure if it will become an issue later down the line or not but thats for later down the line

 

That’s great, I really-opened my ticket this morning. Did it take them long to get the issue resolved?

[tdk1069]

Not really. when USA woke up they did the change, then a few days after of "we tried to contact you to discuss your change" and eventually closed. Script pretty much started working again same day

[Sadiq_to222]

Not really. when USA woke up they did the change, then a few days after of "we tried to contact you to discuss your change" and eventually closed. Script pretty much started working again same day

 

Ah right, hopefully my support agent can sort it out for me!

[ZakFarnworth]

Not really. when USA woke up they did the change, then a few days after of "we tried to contact you to discuss your change" and eventually closed. Script pretty much started working again same day

 

When you ran your script when everything broke, did it come with an error of some sort? When I run mine it runs fine and updates the property in Exchange Online but no signature shows in OWA, that’s what I’ve seen with me. Is that something you had too?

[tdk1069]

Morning,

no error what so ever, in fact you could even query SignatureHTML from Get-MailboxMessageConfiguration and see your alterations but they just wouldn't apply to the browser. My theory is that they are keeping roaming signatures in an array elsewhere and just not utilising SignatureHTML.

 

We weren't mandating signatures till this came in so when we disabled roaming signatures we had a bunch of tickets of signatures reverting back to old ones, I assume when they switched over to roaming any updates just went to the new inaccessible field only.

 

My ideal would be to open up Set-MailboxMessageConfiguration to be able to set the roaming ones but this works here anyway

[ZakFarnworth]

Morning,

no error what so ever, in fact you could even query SignatureHTML from Get-MailboxMessageConfiguration and see your alterations but they just wouldn't apply to the browser. My theory is that they are keeping roaming signatures in an array elsewhere and just not utilising SignatureHTML.

 

We weren't mandating signatures till this came in so when we disabled roaming signatures we had a bunch of tickets of signatures reverting back to old ones, I assume when they switched over to roaming any updates just went to the new inaccessible field only.

 

My ideal would be to open up Set-MailboxMessageConfiguration to be able to set the roaming ones but this works here anyway

 

Afternoon,

 

Yeah that’s exactly what’s happening to me, it runs without an issue, and updates the property when you run the get *edit *cmdlet not omelet* like you did above and tells me it’s updated, but in browser nothing has been set. My support agent is waiting for the tenants team to get back to him or something so looking forward to getting this resolved. Microsoft need to include things as optional if it’s going to break things that customers/schools/businesses depend on.

Edited July 14, 2023 by ZakFarnworth

[ZakFarnworth]

I did that - opened a support ticket to get it disabled and my script carried on working as normal - for now... Unsure if it will become an issue later down the line or not but thats for later down the line

 

My signature scripts are working perfectly, I’m not sure if they have updated office/exchange online to correct the issue or not, or it’s just my tenant that have fixed/disabled.

 

Until I know they’ve fixed the issue for all tenants for definite, I’m happy my signatures are setting perfectly!

[tdk1069]

That's kind of how mine went, just started working and a few days later MS got in touch to ask how they did ...

 

Glad its all working! Script all the things!

[ZakFarnworth]

That's kind of how mine went, just started working and a few days later MS got in touch to ask how they did ...

 

Glad its all working! Script all the things!

 

Yeah, it’s a fairly easy process getting in touch with them and getting it resolved, going to save the case notes and things for when it might happen again.

 

Scripting is the only way to do stuff like this at the moment without paying for a cloud service to do it! MS need to design some sort of portal that allows you to create signatures and set for certain groups etc, would be a great and overall liked feature!