Edit pass Solutions guidance (SharePoint#1803)

* Updates to TOC and edit pass

Search

* Edit pass

* Edit pass of Search doc

* Fixes

* Edit pass

* Fixes

* Edit pass Transform farms

* Edit pass

* Edit pass Replace content types

* Edit pass

* Edit Replace files

* Fixes

* Edit pass

* Edit pass

* Edit Replace lists

* Edit pass

* Edit pass

* Edit pass on Transform sandboxes

* Edit pass

* Edit pass

* Edit pass

* Transform sandbox and farms

* Adjusted table spacing

* Adjusted table spacing 2

Author: Linda-Editor

docs/solution-guidance/Sandbox-Solution-Transformation-Guidance-Event-Receivers.md

@@ -1,59 +1,58 @@
 ---
 title: Sandbox solution transformation guidance - Event receivers
-ms.date: 11/03/2017
+description: Identify options and strategies for replacing existing event receivers from your sandbox solutions.
+ms.date: 5/4/2018
 ---
-# Sandbox solution transformation guidance - Event receivers 
-This article will help you to identify options and strategies on replacing existing event receivers from your sandbox solutions.
 
-_**Applies to:** Add-ins for SharePoint | SharePoint 2013 | SharePoint 2016 | SharePoint Online_
+# Sandbox solution transformation guidance - Event receivers 
 
-Code-based sandbox solutions [were deprecated](https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/) back in 2014 and SharePoint online has started the process to completely remove this capability. Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016.
+The approach you take to handle events in SharePoint is slightly different in the SharePoint Add-in model than it was with Full Trust Code or in coded-sandbox solutions. In typical previous solutions, event receivers were created using the SharePoint Server-Side Object Model and deployed via solutions packages, which executed the code on the SharePoint servers. 
 
-## Summary
+In the SharePoint Add-in model, however, the event receiver implementation executes on the web server that is hosting the event receiver; these are called remote event receivers (RERs). Event receivers can in many cases be replaced with a remote event receiver implementation. 
 
-The approach you take to handle events in SharePoint is slightly different in the SharePoint Add-in model than it was with Full Trust Code or in coded-sandbox solutions. In typical previous solutions, event receivers were created using the SharePoint Server Side Object Model and deployed via solutions packages, which executes the code on the SharePoint servers. In the SharePoint Add-in model; however, the event receiver implementation executes on the web server that is hosting the event receiver and these are called Remote Event Receivers (RER). Event receivers can in many cases be replaced with a remote event receiver implementation. This article describes various options and design considerations.
+This article describes various options and design considerations.
 
+> [!NOTE] 
+> [Code-based sandbox solutions were deprecated](https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/) in 2014, and SharePoint Online has started the process to completely remove this capability. Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016.
 
-## Options for replacing Event Receivers
-<a name="sectionSection2"> </a>
+## Options for replacing event receivers
 
-|**Approach**|**Additional Information**|
+|Approach|More information|
 |:-----|:-----|
-|Remote Event Receiver|</p><lu><li>[Use remote event receivers in SharePoint](https://msdn.microsoft.com/en-us/pnp_articles/use-remote-event-receivers-in-sharepoint)</li><li>[How to use remote event receivers for your SharePoint add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li><li>[Event receivers and list event receivers in the SharePoint Add-in model](https://msdn.microsoft.com/en-us/pnp_articles/event-receiver-and-list-event-receiver-sharepoint-add-in)</li></lu><li>[Auto tagging sample add-in for SharePoint](https://msdn.microsoft.com/en-us/pnp_articles/autotagging-sample-app-for-sharepoint)</li><li>[Handle events in SharePoint Add-ins](https://msdn.microsoft.com/en-us/library/office/jj220048.aspx)</li></lu></p>|
-|WebHooks|<p>WebHooks  for SharePoint are still under development and will be available for preview soon.<lu><li>[Introducing SharePoint WebHooks](http://dev.office.com/blogs/introducing-sharepoint-webhooks)</li></p>
-|Remote Timer Job to monitor changes|<p>Use the **ChangeQuery** object to monitor a site or list for modifications. This pattern is an alternative to Remote Event Receivers<lu><li>[SharePoint List Item Change Monitor](https://github.com/SharePoint/PnP/tree/master/Samples/Core.ListItemChangeMonitor)</li><li>[Remote Timer Job Pattern](https://github.com/SharePoint/PnP/tree/master/Samples/Core.SimpleTimerJob)</p>|
-
-## Design Considerations
-### Remote Event Receivers
-- Requires hosting infrastructure
-- Hosting infrastructure must be highly available
-- The service endpoint that hosts the remote event receiver must be configured for anonymous authentication
-- Requires a trusted 3rd Party certificate if you are using SharePoint Online
-- Not intended for long running operations 
-- Remote Event Receivers that are attached out-side the context of add-in, attached using a console application or PowerShell; will not receive a SharePoint context token when invoked and you must differ to app-only permissions or use the SharePointOnlineCredentials class
-- There is no retry mechanism 
-
-### WebHooks
-- Requires hosting infrastructure
-- Hosting infrastructure must be highly available
-- Does not support synchronous events
-- Process changes after the event has occurred
-- Public preview available in summer 2016 for SharePoint Online
+|Remote event receiver|<ul><li>[Use remote event receivers in SharePoint](use-remote-event-receivers-in-sharepoint.md)</li><li>[How to use remote event receivers for your SharePoint Add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li><li>[Event receivers and list event receivers in the SharePoint Add-in model](event-receiver-and-list-event-receiver-sharepoint-add-in.md)</li><li>[Auto-tagging sample SharePoint Add-in](autotagging-sample-app-for-sharepoint.md)</li><li>[Handle events in SharePoint Add-ins](../sp-add-ins/handle-events-in-sharepoint-add-ins.md)</li></ul>|
+|Webhooks|<ul><li>[Overview of SharePoint webhooks](/apis/webhooks/overview-sharepoint-webhooks)</li><li>[Introducing SharePoint Webhooks](https://dev.office.com/blogs/introducing-sharepoint-webhooks)</li></ul>
+|Remote timer job to monitor changes|<p>Use the **ChangeQuery** object to monitor a site or list for modifications. This pattern is an alternative to remote event receivers.<ul><li>[SharePoint List Item Change Monitor](https://github.com/SharePoint/PnP/tree/master/Samples/Core.ListItemChangeMonitor)</li><li>[Remote Timer Job Pattern](https://github.com/SharePoint/PnP/tree/master/Samples/Core.SimpleTimerJob)</ul></p>|
+
+## Design considerations
+
+### Remote event receivers
+
+- Require hosting infrastructure.
+- Hosting infrastructure must be highly available.
+- The service endpoint that hosts the remote event receiver must be configured for anonymous authentication.
+- Requires a trusted third-party certificate if you are using SharePoint Online.
+- Not intended for long running operations.
+- Remote event receivers that are attached outside the context of add-ins, attached by using a console application or PowerShell will not receive a SharePoint context token when invoked, and you must defer to add-in-only permissions or use the SharePointOnlineCredentials class.
+- There is no retry mechanism. 
+
+### Webhooks
+
+- Require hosting infrastructure.
+- Hosting infrastructure must be highly available.
+- Does not support synchronous events.
+- Process changes after the event has occurred.
 - Not available in SharePoint on-premises builds at this time.
 
-### Remote Timer Job
-- Requires hosting infrastructure
-- Process changes after the event has occurred
-- Uses a polling mechanism to process changes
+### Remote timer job
+
+- Requires hosting infrastructure.
+- Process changes after the event has occurred.
+- Uses a polling mechanism to process changes.
 
 ## Removing your sandbox code from your site
-<a name="sectionSection3"></a>
-When you deactivate your existing sandbox solution from your sites, any assets or files deployed using declarative options will not be removed however, the features in the sandbox solution will automatically be deactivated and the event receiver(s) will be removed. 
+
+When you deactivate your existing sandbox solution from your sites, any assets or files deployed by using declarative options are not removed. However, the features in the sandbox solution are automatically deactivated and the event receiver is removed.
 
 ## See also
-<a name="bk_addresources"> </a>
--  [Removing Code-Based Sandbox Solutions in SharePoint Online](http://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online)
--  [Sandbox solution transformation guidance](https://msdn.microsoft.com/en-us/pnp_articles/sandbox-solution-transformation-guidance)
--  [Remove assembly reference from your Sandbox solution created in Visual Studio](https://support.microsoft.com/en-us/kb/3183084)
--  [Build add-ins for SharePoint](https://msdn.microsoft.com/library/office/fp179930.aspx)
--  [Office 365 development and SharePoint patterns and practices solution guidance](https://msdn.microsoft.com/en-us/pnp_articles/office-365-development-patterns-and-practices-solution-guidance)
+
+- [Transform sandbox solutions to the SharePoint Add-in model](sandbox-solution-transformation-guidance.md)

docs/solution-guidance/Sandbox-Solution-Transformation-Guidance-Feature-Receivers.md

@@ -1,62 +1,62 @@
 ---
 title: Sandbox solution transformation guidance - Feature receivers
-ms.date: 11/03/2017
+description: Learn about the options and strategies of converting existing functionality to SharePoint Add-in model or alternative solutions.
+ms.date: 5/4/2018
 ---
-# Sandbox solution transformation guidance - Feature receivers 
-Transform or convert your code-based sandbox solutions to the SharePoint Add-in model. Learn about the options and strategies of converting existing functionality to SharePoint Add-in model or alternative solutions.
-
-_**Applies to:** Add-ins for SharePoint | SharePoint 2013 | SharePoint 2016 | SharePoint Online_
 
+# Sandbox solution transformation guidance - Feature receivers 
 
-## Summary
 Feature receivers are typically used to apply different kind of configurations or settings to SharePoint sites when feature is activated or when site is created (if feature associated to site template / web template). Feature receivers have been deployed using Sandbox solutions in the SharePoint Online, but since code-based customizations cannot no logner be used, alternative design will need to be taken. 
 
 The approach you take to handle feature receivers in SharePoint is slightly different in the SharePoint Add-in model than it was with Full Trust Code or in coded-sandbox solutions. You will need to re-design the solution in away that you use remote APIs (CSOM/REST) to apply the needed configurations to your sites, which previously existed in the feature receiver(s). 
 
+> [!NOTE] 
+> [Code-based sandbox solutions were deprecated](https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/) in 2014, and SharePoint Online has started the process to completely remove this capability. Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016.
 
-## Options for replacing Feature Receivers
-<a name="sectionSection2"> </a>
+## Options for replacing feature receivers
 
 |**Approach**|**Additional Information**|
 |:-----|:-----|
 |PowerShell based customizations|<p>You use PowerShell scripts to provision new site collections (and potentially sub sites) where needed customizations are applied using remote APIs. Typically this is done by using CSOM/REST directly in the PowerShell scripts or by using PnP PowerShell commands, which provides easy way to modify sites and content remotely.</p><p><lu><li>[PnP provisioning engine](https://github.com/SharePoint/PnP-PowerShell)</li><li>[PnP PowerShell - Getting started with latest updates](http://dev.office.com/blogs/pnp-powershell-getting-started-with-latest-updates)</li></lu></p>|
 |Code based customizations|<p>You can apply the needed customizations also using managed code with remote APIs. This means that you will either apply them as part of the administrative operation when the site is created or you apply customizations to SharePoint, which will hook in your code to be part of the UI elements, like by overiding the sub site creation logic, so that you can associate customizations as part of the provisioning logic.</p><p><lu><li>[Remote provisioning pattern for sub site creation](https://channel9.msdn.com/blogs/OfficeDevPnP/Using-remote-provisioning-pattern-for-sub-site-creation)</li><li>[PnP CSOM Core Component](https://github.com/SharePoint/PnP-sites-core)</li></lu></p>|
 
-## Design Considerations
-### PowerShell based provisioning
+## Design considerations
+
+### PowerShell-based provisioning
+
 This model works great if your site provisioning model is based on administrative actions.
 - Does require script to be executed which applies needed customizations to created sites
 - Can be combined to site creation process, if performed by as administrative operation
 - Does not require hosting infrastructure
 - No way to combine automatically as part of the sub site creation process
 
-### Code based provisioning
+### Code-based provisioning
+
 - Can require hosting infrastructure, if combined with end user operations
 - You can use managed code which is executed anywhere using CSOM/REST APIs for the needed operations
 - Can be used to integrate to SharePoint by overriding sub site creation link
 - You can automate site collection and subsite provisioning using remote APIs
 
-> If you want to provide automatic way to apply needed remote code as part of the sub site creation logic, you'll need to override sub site link using user custom actions. This option is only availale in sites, which are using classic mode around libraries and lists. 
-
+If you want to provide an automatic way to apply needed remote code as part of the sub site creation logic, you'll need to override sub site link using user custom actions. This option is only availale in sites, which are using classic mode around libraries and lists. 
 
 ## Reference approaches
+
 ### Applying needed customizations to sites using PowerShell
 Here's a simple script which is using PnP PowerShell to upload a theme color file from computer to SharePoint Online and activates that in SharePoint site. 
 
-> This sample is using [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell), which provides more than 150 additional PowerShell cmdlets targeted for site configuration and asset management. 
-
-```postscript 
+This sample uses [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell), which provides more than 150 additional PowerShell cmdlets targeted for site configuration and asset management. 
 
+```powershell 
 Connect-SPOnline –Url https://yoursite.sharepoint.com/ –Credentials (Get-Credential)
 Add-SPOFile -Path c:\temp\company.spcolor -Folder /_catalogs/theme/15/
 Set-SPOTheme -ColorPaletteUrl /_catalogs/theme/15/company.spcolor
-
 ```
 
 ### Applying needed customizations to sites using code
+
 Here's a simple code piece which uses SharePoint Online CSOM to activate custom theme by first uploading the assets to SharePoint site and then activating custom theme. 
 
-> This sample is using [PnP CSOM Core Component](https://github.com/SharePoint/PnP-sites-core), which extends the native out-of-the-box operations by introducing additional set of extension methods for common operations. You can perform similar operations also by using native CSOM, but code would be significantly more complex.
+This sample is using [PnP CSOM Core Component](https://github.com/SharePoint/PnP-sites-core), which extends the native out-of-the-box operations by introducing additional set of extension methods for common operations. You can perform similar operations also by using native CSOM, but code would be significantly more complex.
 
 ```csharp
 
@@ -85,15 +85,14 @@ web.SetComposedLookByUrl("Green");
 When you are using code based approaches, we recommend using [PnP provisioning engine](http://dev.office.com/blogs/sharepoint-pnp-remote-provisioning-engine-august-2016) for the template management, which will dramatically simplify the development efforts. 
 
 ## Removing sandbox solution containing feature receiver code from your site
-<a name="sectionSection3"> </a>
+
 If your sandbox solution contains feature receivers logic for feature deactivation and it's important that those are being executed, before code-based support is completely removed, you should ensure that these kind of features are deactivated before the code-based support is disabled from SharePoint Online. You can uninstall sandbox solutions from SharePoint Online after the code-based support is disabled, but your faeture receiver code would not be executed even though features are getting moved from the site. 
 
-When you deactivate your existing sandbox solution from your sites, any assets or files deployed using declarative options will not be removed however, the feature will automatically be deactivated. Execution of the code in the feature receiver, is dependent on the timing when the sandbox solution is deactivated. 
+When you deactivate your existing sandbox solution from your sites, any assets or files deployed by using declarative options are not removed. However, the features in the sandbox solution are automatically deactivated and the event receiver is removed.
 
 
 ## See also
-<a name="bk_addresources"> </a>
--  [Removing Code-Based Sandbox Solutions in SharePoint Online](http://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online)
--  [Sandbox solution transformation guidance](https://msdn.microsoft.com/en-us/pnp_articles/sandbox-solution-transformation-guidance)
--  [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell/blob/master/README.md) - Script based customizations
--  [PnP CSOM Core training](https://blogs.msdn.microsoft.com/vesku/2016/04/12/office-dev-pnp-core-componenttraining-package/) - For code based options
+
+- [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell/blob/master/README.md) - Script based customizations
+- [PnP CSOM Core training](https://blogs.msdn.microsoft.com/vesku/2016/04/12/office-dev-pnp-core-componenttraining-package/) - For code based options
+- [Transform sandbox solutions to the SharePoint Add-in model](sandbox-solution-transformation-guidance.md)