Application Impersonation for Xink Email Signatures in EOL

%3CLINGO-SUB%20id%3D%22lingo-sub-778755%22%20slang%3D%22en-US%22%3EApplication%20Impersonation%20for%20Xink%20Email%20Signatures%20in%20EOL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778755%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20using%20Xink%20for%20our%20email%20signatures%20and%20want%20to%20have%20it%20attach%20the%20signatures%20when%20a%20user%20uses%20Outlook%20(on%20the%20Web).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.xink.io%2Fsupport%2Fsolutions%2Farticles%2F1000157751-how-to-assign-application-impersonation-in-admin-center-office-365-%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThis%20guide%3C%2FA%3Estates%20that%20this%20requires%20a%20(service)%20account%20which%20has%26nbsp%3BApplication%20Impersonation%20set%20up.%20My%20question%20is%20twofold%3A%3C%2FP%3E%3COL%3E%3CLI%3EUpon%20talking%20with%20Xink%20support%20I%20wanted%20to%20check%20whether%20an%20Office%20365%20License%20is%20required%20for%20this%20user%2C%20and%20if%20so%2C%20which%20type%20so%20as%20to%20optimise%20costs%20for%20micro%20organisations.%20The%20screenshot%20in%20the%20guide%20mentions%20Office%20365%20E3%2C%20which%20I%20find%20highly%20illogical.%3C%2FLI%3E%3CLI%3EFrom%20a%20broader%20perspective%3A%20is%26nbsp%3BApplication%20Impersonation%20really%20required%20or%20are%20there%20other%20options%3F%20What%20are%20these%20options%20and%20what%20does%26nbsp%3BApplication%20Impersonation%20bring%20to%20the%20table%20exactly%20for%20this%20use%20case%3F%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-778755%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-778765%22%20slang%3D%22en-US%22%3ERe%3A%20Application%20Impersonation%20for%20Xink%20Email%20Signatures%20in%20EOL%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778765%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F392%22%20target%3D%22_blank%22%3E%40Jeroen%20Huylebroeck%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3E1.)%20It%20is%20-%20you%20need%20a%20mailbox%20which%20has%20login%20credentials.%20However%20I%20have%20never%20heard%20of%20E3%20as%20a%20prerequisite%20-%20when%20I%20typically%20use%20other%20applications%20(I.e.%20for%20signatures%2C%20or%20for%20mailbox%20migrations)%20it's%20usually%20an%20Exchange%20Online%20Plan%201%20licence.%20I%20have%20never%20personally%20tried%20it%2C%20but%20you%20may%20even%20be%20able%20to%20do%20it%20with%20a%20Kiosk%20licence.%20I%20don't%20see%20any%20reason%20personally%20for%20E3.%3CBR%20%2F%3E%3CBR%20%2F%3E2.)%20You%20could%20potentially%20do%20it%20by%20giving%20the%20mailbox%20full%20access%20and%20send%20as%20permissions%20over%20all%20other%20mailboxes.%20The%20only%20downside%20is%20that%20this%20has%20to%20be%20done%20every%20time%20a%20mailbox%20is%20added%20making%20the%20process%20manual%20even%20with%20Powershell.%20By%20giving%20the%20mailbox%20impersonation%20rights%20(either%20via%20the%20Exchange%20Admin%20Centre%20or%20Powershell)%20there%20is%20no%20need%20to%20do%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20answers%20your%20questions.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

We're using Xink for our email signatures and want to have it attach the signatures when a user uses Outlook (on the Web).

 

This guide states that this requires a (service) account which has Application Impersonation set up. My question is twofold:

  1. Upon talking with Xink support I wanted to check whether an Office 365 License is required for this user, and if so, which type so as to optimise costs for micro organisations. The screenshot in the guide mentions Office 365 E3, which I find highly illogical.
  2. From a broader perspective: is Application Impersonation really required or are there other options? What are these options and what does Application Impersonation bring to the table exactly for this use case?
3 Replies
Highlighted
Hi @Deleted,

1.) It is - you need a mailbox which has login credentials. However I have never heard of E3 as a prerequisite - when I typically use other applications (I.e. for signatures, or for mailbox migrations) it's usually an Exchange Online Plan 1 licence. I have never personally tried it, but you may even be able to do it with a Kiosk licence. I don't see any reason personally for E3.

2.) You could potentially do it by giving the mailbox full access and send as permissions over all other mailboxes. The only downside is that this has to be done every time a mailbox is added making the process manual even with Powershell. By giving the mailbox impersonation rights (either via the Exchange Admin Centre or Powershell) there is no need to do this.

Hope that answers your questions.

Best, Chris
Highlighted

Hi @Christopher Hoard ,

 

Thanks for the insights. It seems the Application Impersonation is the way to go then. But it is clearly so that a license is required, as you need to configure it in the Exchange Online configuration. It can't be with an unlicensed service account, right?

Highlighted
Hi Jeroen,

My understanding is that it has to be licenced otherwise you run the risk of licensing issues in an audit. In my experience most organisations double up on a mailbox they already have (I.e. an admin mailbox) or source a spare licence or remove the licence from a user who has left in order to circumvent any licence additions.

Hope that clarifies

Best, Chris