Wednesday, December 28, 2016

Save my email attachments to a SharePoint document library using Microsoft Flow


I was trying Microsoft Flow and I thought of sharing how I did my first Flow App using the template provided by Microsoft.

The template I’m using is “Save email attachments to a SharePoint document library”.


Step 01

Go to and find the “Save email attachments to a SharePoint document library” using the search box or by navigating through all template.


Step 02

Click on the app and you will get a screen as below. Then you have to select “Use this template” option.

MicrosoftFlow1 (1)

Step 03

Click Sign In and then use your Office 365 username and password.

MicrosoftFlow1 (2)

Step 04

The template will be created for you as below.

MicrosoftFlow1 (3)


Step 05

Select Inbox for the folder option. You can select the Inbox by clicking on folder icon.

MicrosoftFlow1 (4)


Step 06

Site URL: Provide the SharePoint site URL

Folder Path: Give the name of the document library where you would like to store the attachments.

File name: You can give any dynamic value or static value. Please note that you can’t store two documents in the same name. So please make sure the name is dynamic.

File Content: Select “Content”

MicrosoftFlow1 (5)

Step 07

Click on “Create Flow” from the top.

MicrosoftFlow1 (6)


Send a mail with attachment and check your SharePoint Document library. There you can find the attachments.


Friday, September 9, 2016

"Your domain doesn't match the expected domain for this app deployment." issue in provider hosted add-in


One of my friend had an issue after deploying his provider hosted add-in in SharePoint on premise environment. He was not able to access list data from the add-in web of the Add-in. I looked at the code and the error was something as below.



Step 01

Get the add-in id by navigating to


App identifier was something like the below and the text which was bolded will be the add-in id.


Step 02

Get the App Domain by going to below url and giving the add-in id which we got from the above.


Step 03

My observation was that the App Domain which was given during registering the add-in was different from the url where the add-in has been hosted.

So, I registered the add-in again in the SharePoint site with the correct IIS host header and redeployed the add-in; which lead to work perfectly.


Thursday, March 31, 2016

“The attribute 'autoeventwireup' is not allowed in this page” issue in SharePoint 2013


Recently we deployed two wsp solutions in an environment. One wsp consists of master page and the other one consists of a site page with code behind where I use events like onclick and all.

After the deployment when I try to access the aspx page we got the above error.


Solution 1.

Remove the code behind file and create a web part and add the web part in the page.You can see my blog post on how to create site page without code behind.

Solution 2.

Go to Site Settings page, under the Site Action section, click Reset to site definition.


Then give your page url and click Reset.


Check your page.

If its still the same give your master page url (which ends with .master) and repeat the above step.

Now your page should work fine.

Tuesday, February 23, 2016

Facebook template is not found in Visual Studio 2015

Problem Background

Today I thought of creating a Facebook app using Facebook template which was available in Visual Studio 2013. Shockingly the template was not available once I select ASP.Net Web Application template and click OK (Screen shot attached).



Then I got to know by searching online that there is a new extension has been released for ASP.Net project templates.

Check out the below link and install the Visual Studio 2015 Extension for ASP.NET Project Templates.

PS: I directly downloaded the extension from the below url and installed it.


Thursday, January 28, 2016

No permission to open O365 SharePoint site in SharePoint Designer


I tried to open a SharePoint Online developer site in SharePoint designer. Unfortunately I got an unauthorized error (403 Forbidden as given in the screen shots below).



Go to Account setting on the left pane and check whether your user information is correct. Once you sing in with correct credentials you can log in to your site.


Wednesday, January 20, 2016

Enable CORS for web API 2 through Azure portal


We can enable Cross-Origin Request (CORS) by adding “Microsoft ASP.Net Cross Origin Support” nuget package. Also we can enable CORS thorough Azure portal if we have deployed our web API 2 in azure as a app service.

Enable CORS for web API 2 through Azure portal
  1. Login to your azure portal through a browser
  2. Go to app services and click on you app service where web api 2 is hosted.
  3. Go to setting page and scroll thorough
  4. You will find API section and under that you will find CORS (I have highlighted in yellow)


  1. Click on CORS and you can add one or more your client apps. Also you can * mark to grant access to all client applications.

Tuesday, January 19, 2016

Cannot open server “” requested by the login. Client with IP address “” is not allowed to access the server issue in Azure SQL Database


I created a windows forms application in my local machine and the database was deployed in Azure. Once I try to access the database from my local machine through the application I got the exception “Cannot open server “” requested by the login. Client with IP address “” is not allowed to access the server issue”. See the screenshot.


Step 1. Login to Azure portal and select your database. I have used the new Azure Portal.
Step 2. Select tools on from top menu.
Step 3. Once you select Tools the window will be expanded and will show “Open in Visual Studio”. Select it.
Step 4. Then click on Configure your firewall.
Step 5. Give any rule name and you can give your IP address range. Note that the Client IP address is your own IP address. You can set the rage using the client IP address shown in the portal.