Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Outlook (Microsoft Store) #18

Open
Vastuney opened this issue Apr 26, 2024 · 6 comments
Open

New Outlook (Microsoft Store) #18

Vastuney opened this issue Apr 26, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@Vastuney
Copy link

Hi,

has anyone found a solution for the new version of outlook from the microsoft store? The signature doesn't even show up in the available ones. For version 16 everything works fine so I think it's a regedit issue

@NikPPPPPP
Copy link

Hi,
Unfortunately the new version of Outlook doesn't look for signatures in %appdata%\Microsoft\Signatures.
The new version of Outlook only uses signatures provided by an Exchange Server.

So there no easy way to include this in a PowerShell script.

The signature can be changed in the admin settings of your Exchange Server.
But don't worry the Exchange Server can be linked to Microsoft Entra (previously known as Azure Active Directory).
You can link your Active Directory to Microsoft Entra.

Here is an Link on how to setup Microsoft Entra: Setup Microsoft Entra

@captainqwerty
Copy link
Owner

Sorry currently the Outlook from the Microsoft store is out of scope for this project. I am currently deploying it in an environment using the new Office 365 office that has outlook signature syncing to see what effects this has.

@blaxxor
Copy link

blaxxor commented May 23, 2024

I modified the code so it matches the name standard for new Outlook and I see the signature in New Outlook but it's not working as intended. I don't know if it is an encoding error or not but I can see the signatures name in New Outlook but the signature text only outputs "ÿþ". It is the same problem in Outlook for web.

We only use classic outlook at our company for now so I have not tried to fix it but a working version for New Outlook would of course be nice.

@captainqwerty
Copy link
Owner

Which version are you using? The older version or the version I released a few days ago? Version 5.0.0 which you can select the encoding using -encoding parameter. I am currently working on the next little update where I hope to fix the newer Outlook properly.

@captainqwerty captainqwerty self-assigned this May 23, 2024
@captainqwerty captainqwerty added the bug Something isn't working label May 23, 2024
@blaxxor
Copy link

blaxxor commented May 23, 2024

Which version are you using? The older version or the version I released a few days ago? Version 5.0.0 which you can select the encoding using -encoding parameter. I am currently working on the next little update where I hope to fix the newer Outlook properly.

I have no tried the new version yet.

I'm using a amateurish modified version of the older one. I've tried changing encoding but the problem is still the same. I don't know if MS do something with the signature when syncing it with roaming profile or If I'm missing some configuration for the signature to display correct on New/Web Outlook.

@captainqwerty
Copy link
Owner

Maybe you could try version 5.0.1 (change brand from main) - dont make any changes and see if it works, like don't try branding it or anything just run it on a test machine and see what happens :) Then we can go from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants