Help Center

HOME Submit a ticket My Tickets
Welcome
Login  Sign up
  1. Discussions
  2. Share an idea or improvement
  3. I have a suggestion
Not Taken

"Non-Licensed"/Shared Users

E
Eric Chalupka
started a topic over 1 year ago

The new outlook add-in works excellently for users with single-mailboxes, but for users that use send-as or send on behalf of, they now have to have a xink license for each email address they can send as vs. before where the xink program allowed a single signature to be applied across any mail account on the computer. Hoping to have a way to insert a xink signature from an already licensed user, or have non-licensed accounts that pull in signatures from other accounts.

  • Jesper Frier
    said about 1 year ago

    Thanks for your input Eric -

    I will check with our dev if the PA functionality is possible via the add-in.

    In the meantime, you can continue to use the client for the users, that is sending on behalf of other users.

    Thanks
    Jesper Frier

  • Jesper Frier
    said 12 months ago

    Hi Eric -

    You can add the email signature for user A to user B when user B send on behalf of user A.
    Both user A and B will require a Xink license.

    Please provide an example where it doesn't work at your end, please.

    Thanks
    Jesper Frier

  • E
    Eric Chalupka
    said 12 months ago

    Hi Jesper,


    This will mean an additional ~50 shared mailbox users that previously have never needed licenses. The users sending mail are already licensed, but the account they are sending from is shared. This change of product capability will impact budgets, big time. I hope your team will reconsider or determine a way to comp an agreed upon number of xink licenses.


    Eric

  • Jesper Frier
    said 12 months ago

    Hi Eric - 


    We didn't change licensing and I need a specific example to understand the changes at your end - Thanks.

    Since this is a public post, I've sent you my personal meeting link to your email to get a better understanding.

    Jesper

  • Jesper Frier
    said 12 months ago

    Hi Eric - 

    A quick meeting summary:

    • You are using the add-in on Mac.
    • When you switch to the shared mailbox in your Outlook on Mac, the add-in disappears, and you cannot select the signature.
    • We agreed that it makes sense because those mailboxes are not in your account.

    Microsoft recently changed where Outlook stores email signatures.
    Outlook now stores the signatures in the mailbox (I believe it's the same for Mac, based on your demonstration).

    • I offered you the shared mailbox licenses for free.
    • You cannot add them to your main account as they are removed with the next AD sync.
    • Instead, I created a FREE MANAGED ACCOUNT for you where you can maintain your shared mailboxes (this account is independent of your main account).

    What's next?

    • You deploy the add-in to the shared mailboxes in the MANAGED ACCOUNT.

    Keep me posted on your progress :) Thanks
    Jesper

  • A
    Aleksey Avdeev
    said 4 months ago

    Hi Jesper.
    Microsoft offers Shared Mailboxes free of charge. So, many people who must send (with SendAs or SendOnBehalf permissions) from the SharedMailboxes also need to sign up  their mails with a signature.

    It will be more logically, that signature license can just follow up the user, but not the Mailbox it is sending from.

    There are many users could get access to one Shared Mailbox in Exchange Environment.

  • Jesper Frier
    said 4 months ago

    Hi Aleksey -

    You can always apply the shared mailbox signatures as OPTIONAL email signatures.
    Then the end-users can select when required.

    The only way to automate the selection is to have the shared mailbox email in your EMPLOYEES list.

    I'll ping our add-in dev team and will provide an update later if there are other possibilities.

    Thanks
    Jesper

  • J
    Johan Mos
    said about 2 months ago

    Any updates yet? At this moment our shared mailboxes are not 'licensed' users and get the mentioned error. In the previous (MSI deployment version) this error did not ocur. 

  • Jesper Frier
    said about 2 months ago

    Hi Johan -

    We were in a dilemma because of mobile support we recently implemented.

    Shared mailbox support requires version 1.13 of Microsoft’s add-in framework (and it will not work with the NEW Outlook which users can select).
    Mobile support requires version 1.5 of Microsoft’s add-in framework..

    We made a decision to support mobile and the NEW Outlook and is waiting for an update from microsoft.
    We expect that Microsoft will update their support for shared mailbox signatures later. We are monitoring but have no ETA from Microsoft.

    Ping me directly via email regarding the licensing.
    Since this is a public post, I will not share my email here.
    Ping our support (chat or email) and they will share my email - Thanks.

    Thank you for your understanding
    Jesper Frier

  • P
    PROXSYS* Service Desk
    said about 2 months ago

    Hi Jesper, thanks for your reply! I meant the addin available through the Microosft 365 addin option (as mentioned in IT Pro: Unattended deployment of Xink Add-in to Office 365 tenant : Help Center). Does this also works with versions? 

    Thanks 

  • Jesper Frier
    said about 1 month ago

    I recommend the manifest version (hosted by Xink) because it's includes more functionalities.
    We face more and more restrictions for the add-in AppSource version (hosted by Microsoft).


    Thanks.
    Jesper

  • P
    PROXSYS* Service Desk
    said about 1 month ago

    Hi Jesper, thanks i updated the app manifest, I've seen that we had an old version of this. i will investigate it later if the new version solves the issues we have. keep you posted! 

Login or Signup to post a comment
Topics in this forum
View all (134)

Didn't find what you were looking for?

Start a new topic

Search articles