Bits and pieces

I have always been fascinated by different authentication mechanisms that Microsoft provides and recently when a colleague of mine was working on a custom connector, I got to assist her with setting up On-behalf of Flow authentication. Custom Connectors are kind of actions provided by 3rd parties that users can use in Microsoft Flows. First of all you need to create a Web API, that will perform the action when someone uses the custom connector. You will need to host this Web API on Azure and create an AAD application that will register the Web API. You will also need create an AAD app that will register the custom connector. You will also need to establish communication between Web API AAD app and Custom Connector AAD App. Steps for this can be found here,  https://hiralpatel-sharepointdevelope.blogspot.com/2019/03/steps-to-create-custom-connector-for.html Basically, here, our client is our custom connector, which communicates with the AAD app hosted on azure to acquire a ac...

The client's requirement was to use a Shared Mailbox which will have multiple alias and according to the alias determine a library on SharePoint and store the email in that library. Now, from flow's action "when a new email arrives in a shared mailbox" you can't determine the email sent to which alias. This is where use of exchange transport rules came to my mind. So, what I did, I created an exchange transport rule for every alias, which will prefix name of the alias to the subject line of the email and then while processing the email in flow I, through some string operations got the name of alias out of the subject line. In the image below, the email was originally sent to alias HRJobs@xyz.com, but when it got to Flow you can see that in the To address, the value is mycompanyjobs@xyz.com, which is address of the Shared mailbox. In the subject line you would see how HRJobs is prefixed. Well, this is it until next time! Thanks for reading.