Updates from: 08/14/2021 03:26:20
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Branding Sharepoint Online Sites Modern Experience https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/branding-sharepoint-online-sites-modern-experience.md
In the modern SharePoint experience, you can easily [change the look](https://su
## Site branding in the classic experience
-In the classic SharePoint experience, there are a set of default themes that can require a considerable amount of customization to get them to match your organization's brand. Also, they aren't very responsive, making the experience on different devices inconsistent. Most site branding requires the use of custom master pages or alternate CSS configurations. Master pages provide a great deal of flexibility, but they can be problematic. For example, anytime updates are made to SharePoint, any customizations made to the master page may no longer work or may not work the way you expect them to. SharePoint [ignores these customizations](/sharepoint/dev/transform/modernize-branding) unless you're running in classic experience mode because they're incompatible with the modern user interface. To avoid this, use only the recommended modern approaches to brand your SharePoint sites.
+In the classic SharePoint experience, there is a set of default themes that can require a considerable amount of customization to get them to match your organization's brand. Also, they aren't very responsive, making the experience on different devices inconsistent. Most site branding requires the use of custom master pages or alternate CSS configurations. Master pages provide a great deal of flexibility, but they can be problematic. For example, anytime updates are made to SharePoint, any customizations made to the master page may no longer work or may not work the way you expect them to. SharePoint [ignores these customizations](/sharepoint/dev/transform/modernize-branding) unless you're running in classic experience mode because they're incompatible with the modern user interface. To avoid this, use only the recommended modern approaches to brand your SharePoint sites.
## Modern site branding
SharePoint includes an updated set of default site themes that are responsive an
When you brand a [SharePoint hub site](https://support.office.com/article/fe26ae84-14b7-45b6-a6d1-948b3966427f), you can set it so the site branding is applied to any sites that [associate with it](https://support.office.com/article/ae0009fd-af04-4d3d-917d-88edb43efc05). This includes any site theme or site design used by the hub site. This allows you to apply common navigation and branding across a set of sites and use accent colors to emphasize elements that need to stand out. > [!NOTE]
-> Custom themes in SharePoint *will not* automatically apply to group-connected team sites that are associated to a hub that has a custom theme applied. For group-connected team sites, you need to manually apply the custom theme.
+> Custom themes and logos in SharePoint *will not* automatically apply to group-connected team sites that are associated to a hub that has a custom theme applied. For group-connected team sites, you need to manually apply the custom theme or logo.
## Classic experience vs. modern experience
SharePoint Create A Giving Site For Your Organization https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/create-a-giving-site-for-your-organization.md
For more information, see [Create a communication site in SharePoint Online](htt
You can quickly and easily customize the organization and navigation of your SharePoint site to make it easy for your visitors to navigate the site and find the information they need.
- ![Image of the Sharepoint navigation tool bar](media/navigation-bar.png)
+ ![Image of the SharePoint navigation tool bar](media/navigation-bar.png)
<br> - **Add and edit the main menu** Easily edit the top menu to link the page to other SharePoint pages or on the Internet. <br>
SharePoint Sharepoint Admin Role https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/sharepoint-admin-role.md
description: "Learn about the SharePoint admin role in Microsoft 365. SharePoint
Global admins in Microsoft 365 can assign users the SharePoint admin role for help with administering Microsoft SharePoint. The global admin role already has all the permissions of the SharePoint admin role. For info about assigning a user the SharePoint admin role, see [Assign admin roles in Microsoft 365 for business](/office365/admin/add-users/assign-admin-roles).
- ![Manage admin roles in the Microsoft 365 admin center](media/sharepoint-admin-role.png)
+![Manage admin roles in the Microsoft 365 admin center](media/sharepoint-admin-role.png)
Users assigned the SharePoint admin role have access to the SharePoint admin center and can create and manage sites (previously called "site collections"), designate site admins, manage sharing settings, and more.
Global admins and SharePoint admins don't have automatic access to all sites and
Site admins are users that have permission to manage sites, including any subsites. They don't need to have an admin role in Microsoft 365, and aren't given access to the SharePoint admin center. > [!NOTE]
-> Global admins, SharePoint admins, and site admins all need to be assigned a SharePoint license. If you have a standalone OneDrive for Business plan, admins can access the SharePoint admin center without a SharePoint license. <br>There is a separate role within SharePoint called the **Term Store administrator**. Users assigned this role can add or change terms in the term store (a directory of common terms you want to use across your organization). To learn more, see [Assign roles and permissions to manage term sets](assign-roles-and-permissions-to-manage-term-sets.md).
+> Global admins, SharePoint admins, and site admins all need to be assigned a SharePoint license. If you have a standalone OneDrive for Business plan, admins can access the SharePoint admin center without a SharePoint license.
+>
+> There is a separate role within SharePoint called the **Term Store administrator**. Users assigned this role can add or change terms in the term store (a directory of common terms you want to use across your organization). To learn more, see [Assign roles and permissions to manage term sets](assign-roles-and-permissions-to-manage-term-sets.md).
## Key tasks of the SharePoint admin <a name="BK_KeyTasks"> </a>
SharePoint Tenant Rename https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/tenant-rename.md
It's now possible to change the SharePoint domain name for your organization in
| Teams on the web and Teams desktop app | On the Files tab, any folders added with the "Add cloud storage" (which point to another SharePoint site) won't work.| Remove and readd the folders. | | Teams on the web and Teams desktop app | Document libraries added as a tab won't work. | Remove and readd the tab. | | Teams on the web and Teams desktop app | Embedded images in Wikis won't be displayed. | Edit the Wiki .mht file located in the SharePoint Site Teams Wiki Data library and if necessary, change the URLs of the embedded images to the new domain name. |
+| Teams on the web and Teams desktop app | Personal Wikis wonΓÇÖt work. | In a one-on-one or group chat, attach and send a file to the chat. |
| Third-party apps including backup solutions | Absolute URLs embedded in these third-party apps (including backup solutions) aren't changed. | Confirm with third-party app publishers (including backup solutions) that they support tenant renames. | ### High impact
SharePoint Prepare Your Environment https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/hybrid/prepare-your-environment.md
description: "Learn how to prepare the on-premises account and security group to
This example of the Microsoft Business Connectivity Services (BCS) hybrid scenario shows you how to use standard Windows domain security to control access to the on-premises OData service endpoint. You configure one domain account with which to access the OData service endpoint, and one global security group for your federated user accounts. Then, you map the group to the account by using a Secure Store Service target application.
-##
-
- **To prepare on-premises security for the BCS hybrid scenario**
+**To prepare on-premises security for the BCS hybrid scenario**
1. Identify all the user accounts in your on-premises domain that need to use the BCS hybrid solution and make sure that they are federated accounts. You will add these accounts to a domain global security group later in this procedure.
This example of the Microsoft Business Connectivity Services (BCS) hybrid scenar
## Create and configure a Secure Store target application
- In this procedure, you link the **ODataGroup** to the **ODataAccount** by using a Secure Store target application. This way, users in the **ODataGroup** access the OData service endpoint through only one account, the **ODataAccount**.
+In this procedure, you link the **ODataGroup** to the **ODataAccount** by using a Secure Store target application. This way, users in the **ODataGroup** access the OData service endpoint through only one account, the **ODataAccount**.
In this procedure, you create and configure the on-premises Secure Store target application named **ODataApp** for the BCS hybrid scenario. (You can choose a different name if you want.)
- **To create a target application**
+**To create a target application**
1. On the Central Administration home page, in the **Application Management** section, select **Manage service applications**.
In this procedure, you create and configure the on-premises Secure Store target
Next, we need to add the credentials that we'll be using.
- **To set credentials for a target application**
+**To set credentials for a target application**
1. In the target application list, point at the target application that you just created, select the arrow that appears, and then, in the menu, select **Set credentials**.
To create and configure the OData service endpoint, perform the procedures in [H
The BCS hybrid scenario publishes on-premises data to select users of SharePoint in Microsoft 365. You can present the data either through a SharePoint in Microsoft 365 external list or through an app for SharePoint in Microsoft 365. In either case, you must identify or create a site in SharePoint in Microsoft 365 through which the data will be offered. If you choose to use an app for SharePoint in Microsoft 365, you must also have a SharePoint in Microsoft 365 App Catalog configured.
- **To prepare the SharePoint in Microsoft 365 site and App Catalog**
+**To prepare the SharePoint in Microsoft 365 site and App Catalog**
1. Identify or [create a site](https://go.microsoft.com/fwlink/?LinkId=288864) in SharePoint in Microsoft 365 for your external list or app for SharePoint in Microsoft 365. Ensure that all the federated users who will be using the BCS hybrid solution are added to the **Members** group for access to the site. (The easiest way to do this is to add your ODataGroup as a Member.)
The BCS hybrid scenario publishes on-premises data to select users of SharePoint
The Business Data Connectivity service (BDC) Metadata Store holds external content types, external systems, and BDC model definitions for the BDC Service Application. In this procedure, you configure administrative permissions on the Metadata Store and everything that it will contain. Later in this scenario, if you are using the manual import of the external content type method, you will be using the BDC Metadata Store. This external content type will be available across SharePoint in Microsoft 365. If you will only be using the automated deployment of an app for SharePoint in Microsoft 365, then you will not use the BDC Metadata Store, and the external content type is scoped to the app only.
- **To set permissions on the BDC Metadata Store in SharePoint in Microsoft 365**
+**To set permissions on the BDC Metadata Store in SharePoint in Microsoft 365**
1. Go to the [More features page of the new SharePoint admin center](https://admin.microsoft.com/sharepoint?page=classicfeatures&modern=true), and sign in with an account that has [admin permissions](../../SharePointOnline/sharepoint-admin-role.md) in Microsoft 365.
Before you begin this procedure, make sure you have the following:
- The credentials of a federated account.
- **To confirm access to external URL**
+**To confirm access to external URL**
1. Copy the certificate to your extranet computer, and then click the certificate. You will be prompted for the certificate password. This adds the certificate to your personal certificate store.
Before you begin this procedure, make sure you have the following:
- The ID of the Secure Store target application for the Secure Channel certificate in Microsoft 365.
- **To configure the connection settings object for the BCS hybrid scenario**
+**To configure the connection settings object for the BCS hybrid scenario**
1. go to the [More features page of the new SharePoint admin center](https://admin.microsoft.com/sharepoint?page=classicfeatures&modern=true), and sign in with an account that has [admin permissions](../../SharePointOnline/sharepoint-admin-role.md) in Microsoft 365.
Before you begin this procedure, make sure you have the following:
6. In the **Service Address** box, enter the URL of the OData service endpoint that you created.
-7. For this scenario, select the **Use credentials stored in Sharepoint on-premises** as the authentication option, and then enter the name of target application ID that holds the group to account mapping. In this scenario, it is **ODataApp** that you created.
+7. For this scenario, select the **Use credentials stored in SharePoint on-premises** as the authentication option, and then enter the name of target application ID that holds the group to account mapping. In this scenario, it is **ODataApp** that you created.
8. In the **Authentication Mode** dropdown, select **Impersonate Window's Identity**.