Anyone figure this out with Sharepoint Online/Office 365?

Jan 28, 2012 at 11:59 PM

The Sharepoint List Source/Destination works just fine against an internal sharepoint 2010 server, but fails with a 403 forbidden code when trying to get to my office 365 site.  I tried all of the different combinations of credentials I could think of:,, DOMAIN\ - and tried with IE9 from the same session to verify I have the right password and URL - but still that crazy 403 error.

Anybody figure this out, or do I need to start custom coding?  If so - anyone want to help me:  as this seems like a huge opportunity to expand this fantastic free product into the solution space currently held only by expensive commercial offerings.



Feb 29, 2012 at 9:49 PM

Ditto ... Have been successfully using the adapter for more than a year on various accounts, but I now need to know if there is an option with 365. I'm assuming that we'll need to ensure that our corporate domain is trusted by 365.


Apr 18, 2012 at 3:32 AM

Interesting scenario. I wish I had an answer for you. 

Feb 27, 2013 at 12:17 AM
I'm stuck here as well. I am sending text files to a doc library in 365 via email and need to pull the files down into SSIS for ETL processing..... keep getting the FORBIDDEN error 403.
Has anyone made any progress on this front?
Sep 5, 2013 at 6:49 PM
I'm having the same issue making a connection. Has anyone solved this?
Sep 10, 2013 at 2:17 PM
Hi I am having the same issue. Can someone help me out? Thanks
Oct 16, 2013 at 3:33 PM
Having the same issue. Please any help would be very appreciated. Thanks
Jul 29, 2015 at 10:57 PM
Any one have any luck with this on O365 yet? We are getting 403 forbidden error as well. Thanks
Aug 13, 2015 at 3:46 PM
Has anyone tried using the Claims formatted account credentials, e.g., i:0#.f|membership|UPN? this is frequently required for O365 credentials.
Nov 12, 2015 at 7:15 PM
It would be nice if someone would at least say whether or not it's meant to work with O365.
Dec 8, 2015 at 5:52 PM
jbrown08322 wrote:
It would be nice if someone would at least say whether or not it's meant to work with O365.
The issues with the Codeplex project have been outlined in this article:

A resolution is also provided by using the ODATA adapter available in SQL 2012 and later.