jseerden / IntuneEmailSignatureManagement

Lightweight tool deployed with Microsoft Intune to manage e-mail signatures for Outlook
MIT License
55 stars 18 forks source link

New Outlook #6

Open SYSMANTEAM opened 9 months ago

SYSMANTEAM commented 9 months ago

Hi, I have been trying to get this to work with New Outlook.

Have you perhaps had a look at this solution for New outlook?

It is very new still and I am not sure if it would even be possible to manage email signatures in the same way with New outlook.

wwa-jvteeffelen commented 8 months ago

I've looked into this myself as well. Outlook seemed to have added the user email to the files and folders related to the signature (in %appdata%\Microsoft\Signatures

It's a bit more hand-work, but I got it working by doing the following:

That should be enough to make it work again. You can check it by manually executing the install.ps1 script with powershell.

SYSMANTEAM commented 8 months ago

Hi, thanks for the feedback, i had a look at the above, and it makes sense that this would work for the latest versions of Outlook using the Roaming signature.

It seems this however does not work for Outlook New, the Latest version of Outlook a user would use when using Copilot, enabled via the toggle in Outlook classic.

Microsoft Outlook Version 1.2023.1129.100 (Production). Client Version is 20231201002.05 .

To me it seems like you can create a Email signature manually, but this is not stored in %appdata%\Microsoft\Signatures, instead it seems to be stored on OWA only.. and replicates from there to all Outlook clients.. I am not sure if you have seen the same?

To me it seems like there is no way to actually manage a corporate Signature when using Outlook New, unless i am missing something?

https://support.microsoft.com/en-us/office/getting-started-with-the-new-outlook-for-windows-656bb8d9-5a60-49b2-a98b-ba7822bc7627

wwa-jvteeffelen commented 8 months ago

I've noticed something identical.

I also noticed it to synchronize signatures at some point. I suspect it to be either on (app) startup or when using the toggle to switch between old and new. It's not ideal, but I do wonder if we can use this functionality to push local to cloud somehow.

But as I'm also still missing local archive files, I recommend users at work to stay on "old" for now.