Comments on OD4B branding support added

Author: VesaJuvonen

docs/solution-guidance/Customization-Options-For-OD4B-Sites.md

@@ -7,6 +7,9 @@ ms.date: 11/03/2017
 ### Summary ###
 OneDrive for Business sites can be customized in Office 365 or with app model in general, based on company requirements. Actual techniques to perform this customization are different than in the on-premises, since only app model techniques can be used. This page contains details on the actual patterns which can be used with app mdoel to customize OneDrive for Business sites. 
 
+> [!IMPORTANT]
+> This **only** applies to *classic* OneDrive for Business experience in the SharePoint Online. If you are using the default "New experience", this is not supported. Modern or new experiences of OneDrive for Business does not support custom branding. Tenant administrators can control the default experience from the SharePoint Online administrative settings.
+
 # Why would you customize OneDrive for Business sites? #
 
 There are numerous different aspects on applying customizations to OneDrive for Business (OD4B) sites. You certainly can customize these sites, since they are SharePoint sites, but at the same time you should always consider the short and long term impact of the customizations. As a rule of a thumb, we would like to give following high level guidelines for customizing OD4B sites. 

docs/solution-guidance/portal-branding.md

@@ -43,7 +43,7 @@ In the following sections, we will discuss how to address these requirements.
 The following general principles should be considered when branding portals in an SharePoint Online environment:
 1. The SharePoint Online service is constantly improving. Updates provisioned to the service may affect DOM structure of out of the box pages, and the content of out of the box files (for example, master pages). Developers must keep this in mind and should not rely on unsupported customization approaches (for example, position of specific element in DOM structure of the page).
 2. Avoid customizing master pages. As mentioned above, updates to the service, may affect the structure of out of the box master pages. If you have implemented custom master page copying the contents of any out of the box master page, you will need to further monitor if this out of the box master page is not updated, and re-implement these changes in your custom master page. Otherwise, some SharePoint functionality may start behaving incorrectly, when your custom master page is in use. That's why customizing master pages leads to additional risks and maintenance costs, and it's recommended to avoid it, when possible.
-3. Customized branding of personal sites (OneDrive for Business sites) is **not** supported. It is allowed to apply custom color schemes via Office 365 tenant level branding settings ([Customize the Office 365 theme for your organization](https://support.office.com/en-us/article/Customize-the-Office-365-theme-for-your-organization-8275da91-7a48-4591-94ab-3123a3f79530))
+3. Customized branding of personal sites (OneDrive for Business sites) is **not** supported. It is allowed to apply custom color schemes via Office 365 tenant level branding settings ([Customize the Office 365 theme for your organization](https://support.office.com/en-us/article/Customize-the-Office-365-theme-for-your-organization-8275da91-7a48-4591-94ab-3123a3f79530)). *Notice* that this applies to the default modern experience of OneDrive for Business.
 4. SharePoint Online portals must be considered as a part of overall Office 365 ecosystem. That's why every portal now has Office 365 Suite Bar, and customizing it is **not** supported (see the section **Office 365 Suite Bar** below).
 5. When planning branding and structure of your navigation component, it is important to follow recommendations outlined in [Portal Navigation article](portal-navigation.md).
 6. When extending portal functionality via custom controls (web parts) it is important to follow recommendations from [Portal Performance article](portal-performance.md).