Differences between SharePoint OnPrem vs SP Online

In this post we are going to explain the difference between SharePoint OnPrem Vs SharePoint Online.

1.  Basic Differences
   

   SP On Premises	SP Online
   The SharePoint server farm is within the corporate network. The IT Support team maintains the SharePoint farm and regularly applies Microsoft patches and updates. On premise, Active directory is used for authentication. Full access to use and customize any SharePoint feature as needed. Availability of Enterprise level services such as BCS, Performance Point, etc.	The SharePoint sites reside in the   Microsoft Data Centre (MDC). Microsoft applies the patch regularly. Microsoft’s SLA ensures 99.9%     availability. Microsoft’s global network of data centers provides reduced latency and high network bandwidth. Support for Client Side Object & App model.

2. Feature Comparisons  – All the basic functionality of SharePoint remains the same, there are a number of significant feature differences between On Premises and Online
   

   Category	On Premises	Online
   Product Features	Support for enterprise feature, Office web App (OWA) needs to be installed	Missing or limited features, pre-configured features
   Infrastructure deployment & maintenance	IT Support Team to deploy/manage farm, latest updates or patches not always deployed.	Microsoft manages the environment and ensures all updates and patches are deployed.
   Business Continuity (BC)	Dependent on internal capabilities.	Microsoft built-in redundancy and failover for data centers, but does not provide end user backups or data recovery.
   Cost Involved	Purchase/Maintain Hardware, Software licenses etc.	Annual subscriptions for Office 365 Plans billed on a per user basis.
   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
   Compliance Standard	Dependent on internal capabilities.	Verified by third party authors
   Information Security	Dependent on internal capabilities.	Information in MDS meets industry-specific security standards
   Storage needs	Expensive storage devices, Site Collection -More than 100GB, Scalable Storage Size	Cheap storage cost, Site Collection- up to 100Gb, Maximum content in single tenant -O365 plan based
   Development	Full trust solution can be deployed- Features in farm solutions can have scope as wide as the site collection, web application, or whole farm Public facing website with much of customization is possible Custom “Managed Path” allowed More control can be delegated to power users	Full trust solution and Sandbox cannot be deployed- Allowed More control cannot be delegated to power users and maxim privilege level is Site Collection level.

   
   
3. Technical Comparisons –
   

   Services	Online	On Premises
   Search	Limited access to query	Full text Query
   InfoPath Form Services	Only in E3, E4 and K1 plans	Required License to use InfoPath Form Services
   Claim Bases Authentication	N/A	Can use SQL , LDAP and AD authentication
   Managed Accounts	N/A	Provides a Managed Account to user at access the SP Admin Services
   Usage reporting and Logging	N/A	Provides LOGS and Reporting to check the exceptions and System Report.
   Alternate Access Mapping	N/A	Provides a map requests where the URL of a Web request received by Internet Information Services (IIS) differs from the URL that was typed by a user
   SharePoint Health Analyser	N/A	Site collection pre-upgrade health check examines a site collection and then generates a report listing ay potential upgrade issues and how to address the issues

   
   
4. SharePoint OnPrem Prons and Cons
   

   Pros	Cons
   Control Performance	Cost of internal resources (staff, hardware, software, etc)
   Scale Up and Scale Out	Additional Geographic redundancy costs
   Reduces Bandwidth requirements	Disaster Recovery dependent on internal capabilities
   Fully Customizable	Scale Up/Out Cost( SW/HW)
   Full Server and SQL Database	Patching Servers/farms
   Migrate as Needed	Extra configurations for External Collaboration
   Seamless Single Sign on with Corporate Active Directory

5.  SharePoint Online Prons and Cons
   

   Pros	Cons
   Uptime 99.99%	More ISP Bandwidth
   Multiple Data centers	Limited Customizations
   Geographically redundant	Possible Storage Costs
   Shorted release cycle	Recovery SLAs
   Managed Services (SaaS)	No Server access
   Pay as you go (Low Cost)
   Reduced impact on internal IT resources
   Scalability

Creating Client Web Part in SharePoint Online

Creating Client Web part in Office 365

Hello Everyone in this article I am going to explain how to create webpart in office 365 using JavaScript object model in this article you would be able to see the walk through of the SharePoint Hosted Add-Ins and the process of creating client webpart and custom action.

1.      Open the visual studio - Create SharePoint Hosted App Project Select SharePoint Hosted Add-Ins enter name click Ok

2.       So now enter your site name where you wanted to debug your App and select the hosting environment type so I am, going the select SharePoint Hosted Add-Ins

3.       Now Click on next button enter your valid credential to connect with your SharePoint Online site

Once you complete everything click on finish. It will create SharePoint Hosted App Project. Now follow the next step to add client webpart in your project

       Right click on project – Click add new Item choose Client Webpart(HostWeb)

 

Now it will open the next wizard here you can enter the new page name where you wish to show the app part in my case I am selecting the existing page from solution

Now click on the finish client app part will be added in the solution as shown below

Now let’s create a custom property in client app part. I have added six properties in my webpart as shown below

To read the values from properties I am going the write a custom JS script to get the values

after reading all the values from webpart I am going to create a custom action dynamically on the configured list.

 After writing your complete code and your business logic deploy your app to the SharePoint online and install in your environment.

Follow the below steps to add and configure your webpart on the page

1.       Click on edit page -click on apps selected your recently deployed app from app gallery and add it to the page.

2.       Now configure your custom properties which you have created and click on Apply/Ok

After the above configuration you can see see the custom action created on your list as shown in below screenshot.

Click on the above ribbon buttons – below screen will appear .

Hope this article will help in creating client webpart in SharePoint Online.

Feel free to drop your comments below .

Happy Coding !!