12-14-2016 11:57 PM
Im not sure if this is the right place discuss this, but ill give it a shot.
Im developing an internal application that leverages Azure Active directory for identity management, and Office 365 for mail and calendar (via the graph api). My goal is to manage the signature for all my users via some kind of API also. All my google skills cannot turn up any definitive answer on this topic, not even how to manage it through some admin-panel. This surely must be a thing!? The only solution ive seen is to use a discalimer transport rule (that only can be appended to the end of emails, and cannot feature per-user images, and the user cannot see this signature).
Surely office 365 can have a centrally managed signature, thats appended to any platform using it. Do i have the wrong product (Office 365 Business Essentials for testing purposes)? Am i missin some administration panel?
A company with thousands of employees - how do they manage email signatures? Send some guy to open their email clients on all devices and type them in? Copying and pasting images and what-not. What am i missing?
12-15-2016 06:20 AM - edited 12-15-2016 06:22 AM
Easy answer, no there isnt a built in way to manage signatures like this - you have to go 3rd party providers in general
The APIs should allow you to set signatures in OWA on a per user basis, and then you have to come up with some kind of way to set them in the Outlook client, maybe client install, or group policy or something similar.
12-15-2016 07:08 AM - edited 12-15-2016 07:10 AM
Thank you for the promt reply, and insight into the problem. Great to hear from someone with experience. I cannot find any endpoints for the OWA signatures. There is a new mailboxSettings object in Graph/o365 api but that just contains autoresponses.
How are the third party providers doing it? My development team must be able to implement a similar solution as anyone else, or are the third party providers bying into some other kind of access to my tenant/exchange?
heres the settings object for anyone looking: https://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/mailboxsettings
12-15-2016 07:16 AM
12-15-2016 11:49 AM
12-16-2016 03:06 AM
12-16-2016 03:18 AM
12-16-2016 11:05 AM
12-17-2016 03:04 AM
Code Two also provide centralized control over email signatures: http://www.codetwo.com/exchange-rules-pro/
Generally speaking, you can approach the problem in three ways:
1. Let the users do their own thing - provide them with a prototype signature file on a periodic basis and ask them to update via Outlook/OWA. This is quick, cheap, and users can modify the signature. However, it doesn't ensure consistency and users are prone to forget to apply the update.
2. Use Exchange Transport Rules - you will be guaranteed that signatures are stamped on all outgoing messages and if your Active Directory is correctly populated with the attributes you want to include (like phone number), the outbound signature will be complete. The advantage of this approach is a guaranteed consistency in signatures. The downside is that users don't get to vote and that they might add their own signature to the mix. Also, remember that ETRs can't process signed or encrypted messages.
3. Use a commerical product - you pay for someone else to do all the development, but you get the advantages of years of experience and tons of experience gained from other customer engagements. If signature consistency is important to you, this is the route you should take.
TR
04-18-2017 02:49 AM
Late Reply, but I have done a similar project recently
We handle outlook from group policy logon scripts
OWA is handled through POweshell from which we upload the signature of the user
mobile clients (Android etc) we are also looking for a solution
06-03-2020 03:13 PM
12-11-2020 09:27 AM