Centralized e-mail signature

Question

Hello everyone, I have a "little" problem. I created a centralized company signature (in Office 365) for emails from within EXCHANGE ADMINISTRATION INTERFACE --> RULES and using the APPLY DISCLAIMER TO MESSAGE option The signature was created in HTML format Everything works perfectly However, I need the signature to be encoded with a specific font, so I used the following tag: <FONT face="font_name"> COMPANY_SIGNATURE </FONT> but the encoding does not happen. At this point I have the following doubts and questions:

1. Did I do something wrong in the configuration?
2. Can a particular font be installed in the cloud so that the font is detected by the system and used to encode the signature?
3. Or do you have to install the font locally for the signature to be encoded? If I use Microsoft Outlook 365 off-line, when composing the email I don't see the signature, which will therefore be associated by the cloud mail server, but the end users of the email see it, so I think that the font must be installed at cloud level, but if so I can't figure out how this can be done. Has anyone ever encountered this problem, or has ever faced this situation? And if so, how did you solve it? Thank you all for the time you want to dedicate to me

Answer 1

Hi  @Pierpaolo Casarola , Please try the following encoding format: <p style="font-family:xxx">This is a paragraph.</p>. Below is my test:

Can a particular font be installed in the cloud so that the font is detected by the system and used to encode the signature?

You can check out this article on this question. While fonts in the cloud can be used without embedding in the latest versions of Office applications, custom fonts still need to be embedded for the end user.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.