none
FIM Outlook add-in w/ Exchange 2010 hybrid to O365 RRS feed

  • Question

  • We have a hybrid Exchange environment with Office365.  I started noticing the "approve/deny" buttons provided by the Outlook FIM plugin no longer worked.  The error shown is "This request cannot be approved or rejected because it was received from an unauthenticated sender."

    What I figured out was my mailbox is in the cloud but the FIM service's mailbox is on-prem, so technically they are from different Exchange orgs and hence the sender is no longer validated since its like an external sender.

    Has this scenario been seen by anyone else or addressed already by MS teams?  Is there any way to relax the security on the FIM plugin itself to not do this check as a workaround?  I checked through some reg keys and unfortunately didn't find any setting saying "VerifySender=NO"

    Tuesday, November 5, 2013 7:30 PM

Answers

  • This issue is resolved, and may not have been an unexpected behavior afterall.  After a full directory sync between the on-prem AD and O365, the addresses in the GAL appears normal and no longer showed the smtp address in brackets like it does for external senders.

    there may have just been an inconsistency in the x500 / exchange addresses in the objects, so after a full sync cycle, its been fine, so this scenario should work no problem for others.

    • Marked as answer by renhsrakJ Wednesday, September 3, 2014 2:58 PM
    Wednesday, September 3, 2014 2:58 PM

All replies

  • AFAIK this is not yet supported

    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

    Wednesday, November 6, 2013 10:59 PM
  • This issue is resolved, and may not have been an unexpected behavior afterall.  After a full directory sync between the on-prem AD and O365, the addresses in the GAL appears normal and no longer showed the smtp address in brackets like it does for external senders.

    there may have just been an inconsistency in the x500 / exchange addresses in the objects, so after a full sync cycle, its been fine, so this scenario should work no problem for others.

    • Marked as answer by renhsrakJ Wednesday, September 3, 2014 2:58 PM
    Wednesday, September 3, 2014 2:58 PM