Doc updates to remove tenant level opt out of lists and libraries

jansenbe · jansenbe · commit bb235970c162 · 2019-03-05T08:59:15.000+01:00
diff --git a/docs/solution-guidance/modern-experience-customizations-customize-lists-and-libraries.md b/docs/solution-guidance/modern-experience-customizations-customize-lists-and-libraries.md
@@ -1,7 +1,7 @@
 ---
 title: Customizing "modern" lists and libraries
 description: Get a faster, more intuitive, and responsive SharePoint Online experience by customizing your lists and libraries to the "modern" experience using user custom actions and custom branding.
-ms.date: 11/09/2017
+ms.date: 03/04/2019
 localization_priority: Priority
 ---
 
@@ -270,72 +270,7 @@ If your site happens to use a custom theme, this custom theme is respected in th
 <a name="configuremodernlibrariesandlists"> </a>
 ## Configure the end user experience
 
-You have multiple options to control whether the "modern" or "classic" library and list experience is used. 
-
-### Tenant level configuration
-If you want to completely disable the "modern" experience, it's best to use the tenant setting for this. Go to your tenant admin center (for example, contoso-admin.sharepoint.com), go to Settings, and select the "classic" experience.
-
-**SharePoint lists and libraries experience settings in the SharePoint Admin UI**
-
-![SharePoint lists and libraries experience settings in the SharePoint Admin UI](media/modern-experiences/lists-libraries-tenant-settings.png)
-
-> [!NOTE]
-> - When you switch between **New experience (auto detect)** and **Classic experience**, the change is not immediately visible.
-> - When you select **New experience (auto detect)**, you always see the **Return to classic SharePoint** option. This is by design given that today not all functionalities of "classic" lists and libraries are implemented in the "modern" lists and libraries. There's no option to change this behavior.
-
-### Site/Web level configuration
-You can prevent a site collection or web from using the "modern" experience by enabling a feature:
-
-- For site collection control, use the site collection scoped feature with ID **E3540C7D-6BEA-403C-A224-1A12EAFEE4C4**. 
-- For web control, use the web scoped feature with ID **52E14B6F-B1BB-4969-B89B-C4FAA56745EF**. 
-
-Use the following [PnP PowerShell](http://aka.ms/sppnp-powershell) to enable/disable the needed features:
-
-```powershell
-# Connect to a site
-$cred = Get-Credential
-Connect-PnPOnline -Url https://[tenant].sharepoint.com/sites/siteurl -Credentials $cred
-
-# Prevent modern lists and libraries at site collection level
-Enable-PnPFeature -Identity E3540C7D-6BEA-403C-A224-1A12EAFEE4C4 -Scope Site 
-# And again enable modern lists and libraries at site collection level
-#Disable-PnPFeature -Identity E3540C7D-6BEA-403C-A224-1A12EAFEE4C4 -Scope Site 
-
-# Prevent modern lists and libraries at web level
-#Enable-PnPFeature -Identity 52E14B6F-B1BB-4969-B89B-C4FAA56745EF  -Scope Web 
-# And again enable modern lists and libraries at web
-#Disable-PnPFeature -Identity 52E14B6F-B1BB-4969-B89B-C4FAA56745EF  -Scope Web 
-```
-
-### List/Library configuration
-If you want to control the experience at the library level, you can go to **List settings** > **Advanced settings**, and change the behavior.
-
-**List experience configuration in the SharePoint tenant level settings in Admin UI**
-
-![List experience configuration in the SharePoint tenant level settings in Admin UI](media/modern-experiences/list-experience-setting.png)
-
-The same can also be done by using CSOM as shown in this snippet:
-
-```csharp
-// Load the list you want to update
-var list = context.Web.Lists.GetByTitle(title);
-context.Load(list);
-context.ExecuteQuery();
-
-// Possible options are Auto (= what it's defined at tenant level), NewExperience (= "modern") and ClassicExperience
-list.ListExperienceOptions = ListExperience.ClassicExperience;
-
-// Persist the changes
-list.Update();
-context.ExecuteQuery();
-```
-
-> [!NOTE]
-> - The settings at the library level *override* the settings at the web, site, or tenant level. This also implies that you could pilot the "modern" list and library experience to a subsite of sites by having the "modern" experience turned off at the tenant level but enabled at the list level on the pilot sites.
-> - When you've manually chosen "classic" (that is, not due to list, site, web, or tenant "classic" enforcement), you'll see the link **Exit classic experience** appearing under the left navigation (as of July 2017). Selecting this brings you back to the "modern" experience.
-> - If you're not able to get the "modern" experience to appear, inspect the cookies being passed to SharePoint because it is possible that the opt out of "modern" experiences cookie (splnu with value set to 0) is still present. Clearing the browser cookies should fix this.
-
-<a name="autodetect"> </a>
+You have multiple options to control whether the "modern" or "classic" library and list experience is used. Check out the [Opting out of the modern list and library experience](../transform/modernize-userinterface-lists-and-libraries-optout.md) article for more details.
 
 ## When does the built-in auto-detect automatically switch rendering back to "classic"?
 
diff --git a/docs/solution-guidance/modern-experience-customizations.md b/docs/solution-guidance/modern-experience-customizations.md
@@ -1,7 +1,7 @@
 ---
 title: Customizing the "modern" experiences in SharePoint Online
 description: An overview to get you started using the "modern" experiences in SharePoint Online.
-ms.date: 5/10/2017
+ms.date: 03/04/2019
 localization_priority: Priority
 ---
 
@@ -53,7 +53,7 @@ Following are the key scenarios currently supported by the "modern" experiences.
 
 Existing collaboration sites cannot be converted to "modern" team sites with an associated Office 365 group, but you can however [associate a new Office 365 group](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-connect-to-office365-group) to existing collaboration site. You can also start using modern page and list experiences in the classic sites, which will make them look like a modern group associated team sites.
 
-"Modern" lists and library usage can be controlled at the tenant, site, web, and list/library level. You can find more details about the available options in our ["modern" list and libraries](modern-experience-customizations-customize-lists-and-libraries.md) article.
+"Modern" lists and library usage can be controlled at site, web, and list/library level. You can find more details about the available options in our ["modern" list and libraries](modern-experience-customizations-customize-lists-and-libraries.md) article.
 
 By default, "classic" SharePoint sites use modern pages for any newly added page, and you have the option to change the welcome page to a modern page. Setting a new "modern" page for a "classic" SharePoint site can be done programatically by using CSOM or REST APIs.
 
diff --git a/docs/transform/media/modernize/modernuirollout_1_update.png b/docs/transform/media/modernize/modernuirollout_1_update.png
diff --git a/docs/transform/media/modernize/modernuirollout_2_update.png b/docs/transform/media/modernize/modernuirollout_2_update.png
diff --git a/docs/transform/modernize-classic-sites.md b/docs/transform/modernize-classic-sites.md
@@ -1,7 +1,7 @@
 ---
 title: Modernize your classic SharePoint sites
 description: Steps to transform your SharePoint classic site into a modern Office 365 group-connected team site or communication site.
-ms.date: 04/23/2018
+ms.date: 03/04/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -22,7 +22,7 @@ All of this is great, but you might ask yourself, *I have lots of classic (team)
 
 ## Enable your site to fully leverage the modern user interface
 
-The most visible aspect of a modern site is its modern user interface. If you haven't turned off the modern experience at the tenant level (the **SharePoint Lists and Libraries experience** setting in the tenant admin center), certain pages appear in the modern user interface:
+The most visible aspect of a modern site is its modern user interface. If you haven't turned off the modern experience, certain pages appear in the modern user interface:
 
 - List and library pages for most lists and libraries
 - Site contents page
@@ -34,8 +34,6 @@ However, if you navigate your site, you will notice that the following pages sti
 - Home page and all other site pages (wiki pages and/or web part pages)
 - List and library pages for certain lists and libraries
 
-You probably already have the out-of-the-box modern user interface for lists and libraries enabled at the tenant level, so it makes sense to further maximize its use. SharePoint tries to show your lists and libraries by using the modern user interface, but you might have customizations or configurations that prevent this.
-
 To maximize the use of the modern user interface for your site pages and list and library pages, see [Modernize the user interface](modernize-userinterface.md).
 
 To learn more about how to unblock your lists and libraries when using the modern user interface, see [Maximize use of modern lists and libraries](modernize-userinterface-lists-and-libraries.md).
diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md b/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md
@@ -10,14 +10,14 @@ localization_priority: Normal
 
 The modern list and library experience is enabled by default and for most customers this is a good model as that immediately brings the benefits of the modern list and library user interface. If you however want to more control of the rollout you can adopt one of the below described approaches.
 
-## Approach 1: the default approach
+## Approach 1: recommended, the default approach
 
-In this approach we leave the modern list and library experience active at tenant level but do run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) to understand which lists are not yet ready for the modern experience. If a site contains multiple of these lists or if the users of a given site are not yet ready for modern you can selectively disable the modern experience for that site. This gives you the needed time to remediate the lists or to educate the users so that later on you can enable the modern experience again.
+In this approach we do run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) to understand which lists are not yet ready for the modern experience. If a site contains multiple of these lists or if the users of a given site are not yet ready for modern you can selectively disable the modern experience for that site. This gives you the needed time to remediate the lists or to educate the users so that later on you can enable the modern experience again.
 
-![The default approach](media/modernize/modernuirollout_1.png)
+![The default approach](media/modernize/modernuirollout_1_update.png)
 
 ## Approach 2: the "full control" approach
 
-If you want to only enable the modern list and library experience after you've ensured the lists and your users are ready for it you can opt for this "full control" approach. You start with disabling the modern list experience at tenant level (you probably already did this) and then enable the modern experience site level blocking feature. Once you've blocked the modern experience for all sites you can enable modern at tenant level. At this point all sites will still use the classic list experience but it does allow you to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) and remediate the needed lists. Once the lists and your users are ready you can selectively again disable the modern experience site level blocking feature. Recommended is to do this work in a number of waves until all sites are using the modern list and library experience.
+If you want to only enable the modern list and library experience after you've ensured the lists and your users are ready for it you can opt for this "full control" approach. You start with disabling the modern list experience at site collection level by enabling the modern experience site level blocking feature. At this point all sites will still use the classic list experience but it does allow you to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) and remediate the needed lists. Once the lists and your users are ready you can selectively again disable the modern experience site level blocking feature. Recommended is to do this work in a number of waves until all sites are using the modern list and library experience.
 
-![The full control approach](media/modernize/modernuirollout_2.png)
+![The full control approach](media/modernize/modernuirollout_2_update.png)
diff --git a/docs/transform/modernize-userinterface-lists-and-libraries.md b/docs/transform/modernize-userinterface-lists-and-libraries.md
@@ -37,7 +37,7 @@ Following are the most commonly used list template types that SharePoint can cur
 In this section you'll learn how to identify lists which are not showing as a modern list, why that is and how to remediate those (if possible). However before jumping into this, it's important to realize that for most tenants we see the majority of the lists loading in modern without any caveats. Lists that don't load in modern either stay in classic (like the calendar or tasks list) or can be unblocked by remediating them, which is the scope of this article series. Lists which do not load as modern list are 100% fine to use, fully supported and they should not hold you back from enabling the modern list and library experience for your tenant.
 
 > [!IMPORTANT]
-> For most tenants there are not that many lists that require remediation and as such **our recommendation is to enable the modern list and library experience at tenant level**. This will ensure that all lists that can use modern present themselves as a modern list while lists that cannot simply switch to classic when you use them.
+> SharePoint will automatically default to modern lists and libraries, but will also automatically fallback when needed. This will ensure that all lists that can use modern present themselves as a modern list while lists that cannot simply switch to classic when you use them.
 
 ## Detect lists and libraries not available in the modern user interface
 
@@ -100,7 +100,7 @@ var list = context.Web.Lists.GetByTitle(title);
 context.Load(list);
 context.ExecuteQuery();
 
-// Possible options are Auto (= what it's defined at tenant level), NewExperience (= "modern") and ClassicExperience
+// Possible options are Auto (= defaults to modern), NewExperience (= "modern") and ClassicExperience
 list.ListExperienceOptions = ListExperience.Auto;
 
 // Persist the changes
