We have sharepoint 2013 on premise based product development in workflows and core sharepoint stuff.

Is office 365 ready in all terms to move to office 365 from on premise product dev in sharepoint?

We do not want to use numerous workarounds or gotchas or limitations.

What we need is full fleded development plus social plus mobile ready plus api support just like onpremise sharepoint 2013 or salesforce.com plus dashboarding(may be Po

so you're wondering if using O365 is going to give you the same capabilities as on-prem?

no.

MS is closing the gap on what can and can't be done... but there are still NOTABLE differences.

Those differences are WELL documented online... a simple search will provide you with the information you seek.

Thanks Scott! So we will wait and watch for 1/2 years...

so we have multiple sql server databases, multiple workflows plus dashbaords in tableau, multiple custom web parts and forms.

Hi,

There are some differences between SharePoint On Premises and SharePoint online.

More information for your reference:

http://www.cloudally.com/sharepoint-on-premises-vs-sharepoint-online-2013/

Best Regards,

Dean Wang

Thanks Dean!

Customization Options

Full support for server side code and client side code, App usage from OAC and SAS

Full Support- Client Side, Limited Support-Server side, Can use Apps from OAC or SAS

Does this mean we can write full client object model code in sp online?

Hi Amit,

>> Does this mean we can write full client object model code in sp online?

Yes.

An article about SharePoint online development for your reference:

https://technet.microsoft.com/en-us/library/sharepoint-online-developer-service-description.aspx?f=255&MSPPError=-2147217396

Best Regards,

Dean Wang

so can I propose to my team to move all the logic to client object model(c# based or js based) and web service and then we will also create new designer workflows in office 365 plus lists. Do we have to host SQL custom tables in office 365? or can we host our current tables in on premise and query from there?

Also how to manage dev, QA, UAT and production releases and redeployments in office 365 based development?

I think office 365 is great candidate for future development. I am just worried about gotchas and limita

Suppose we have 8 clients how do we create seperate web apps in office 365 for these 8 clients?

if there is SSO(saml2.0) where client will autologin to our site how it can be achieved in office 365(currently we do this on on premises either using adfs saml2.0 or ping federate)?

Can we separate these 8 accounts in office 365 AD and SQL instances?

also how to deploy designer workflows/wsp solutions from dev to qa and production?

how will per user license works for these 8 clients?

also our product has users in SQL database and we use custom STS, how can we use custom STS to do SSO and let user login with database credentials into office 365?

Hi Amit,

Thanks for considering to move to cloud for your on-premises environment. Actually Microsoft does encourage customers to go to cloud, which should be more easier for management and cost saving.  Here are my suggestions:

Suppose we have 8 clients how do we create seperate web apps in office 365 for these 8 clients?

In Office 365, you can get one separate tenant for each client, and it is just like a multiple tenants environment in on-premises. 

if there is SSO(saml2.0) where client will autologin to our site how it can be achieved in office 365(currently we do this on on premises either using adfs saml2.0 or ping federate)?

Single Sign-On is supported in Office 365(by ADFS only). This needs to sync your on-premises Active Directory to Windows Azure AD. See Office 365 SSO Content Map: https://community.office365.com/en-us/w/sso/office-365-sso-content-map

Can we separate these 8 accounts in office 365 AD and SQL instances?

As long as you set up separate tenants for these accounts, their accounts are also managed separately.

also how to deploy designer workflows/wsp solutions from dev to qa and production?

The method for deploying workflow from dev to QA and production should be similar as on-premises, and you can use export/import VISIO format. Farm solution is not supported in SharePoint Online, but sandbox solutions are allowed. You may consider more things with App format to take advantage of the flexibility and new APIs(such as Office 365 unified API).

how will per user license works for these 8 clients?

Per user consumes per Office 365 package license or a single license for SharePoint Online.

also our product has users in SQL database and we use custom STS, how can we use custom STS to do SSO and let user login with database credentials into office 365?

Custom STS is currently not supported in Office 365, however, SharePoint Online allow inviting external users with limited access. You may consider to convert the SQL users to external users. How to enable external sharing in SharePoint Online with PowerShell

In addition, Office 365 also allows to integrate the current on-premises SharePoint environment and SharePoint Online as a hybrid solution. By doing this, you can mostly keep the current infrastructure, and take advantage of the great features in SharePoint Online.

Hybrid for SharePoint Server 2013
https://technet.microsoft.com/en-us/library/jj838715.aspx

Thanks,
Reken Liu

Great answers Reken. Thanks!

just one more query- in on premises 2013 workflows can be deployed as STP solution. How office 365 workflows can be deployed?

Visio does not export/import all actions. Do we have to rebuild designer workflow 4 times if we have dev/qa/uat/prod?

Hi Amit,

I have followed steps in this article for testing STP solution:

http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/30/packaging-list-site-and-reusable-workflow-and-how-to-deploy-the-package.aspx

It works like a charm.

Best Regards,
Reken Liu