| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Publishing Sites Classic To Modern Experience | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/publishing-sites-classic-to-modern-experience.md | Traditionally, sites and pages like this have been designed and built using the - **Save Site as a template** ΓÇô The save site as a template feature is not supported on a modern communication site. For more info, see [Save, download, and upload a SharePoint site as a template](/sharepoint/dev/general-development/save-download-and-upload-a-sharepoint-site-as-a-template). - **Save List/Library as a template** ΓÇô The save list as a template feature will only work when custom scripts are allowed. For more info, see [Allow or prevent custom script](./allow-or-prevent-custom-script.md). - **Reset to Site Definition** ΓÇô The reset to site definition feature is not supported on a modern communication site. -- **Classic Record Center** ΓÇô The Record Center feature is not supported on a modern communication site. Instead, use the modern records management capabilities. For more info, see [Records Management in Microsoft 365](/microsoft-365/compliance/records-management) and [Learn about Records](/microsoft-365/compliance/records). +- **Classic Record Center** ΓÇô The Record Center feature is not supported on a modern communication site. Instead, use the modern records management capabilities. For more info, see [Microsoft Purview Records Management](/microsoft-365/compliance/records-management) and [Learn about Records](/microsoft-365/compliance/records). - **SharePoint 2010 and 2013 Workflows** ΓÇô SharePoint 2010 and 2013 Workflows are not supported with modern communication sites. Instead, use Microsoft Power Automate. For more info, see Microsoft [Power Automate](https://flow.microsoft.com/) and [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f). - **Subsites** ΓÇô The subsite feature is not supported on modern communication sites but is supported on Teams sites. Creation of subsites is available but not recommended. Consider using the modern hub site feature instead. For more info, see [What is a SharePoint hub site?](https://support.microsoft.com/office/what-is-a-sharepoint-hub-site-fe26ae84-14b7-45b6-a6d1-948b3966427f?ui=en-us&rs=en-us&ad=us). |
| SharePoint | Teams Connected Sites | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/teams-connected-sites.md | Title: Teams and SharePoint integration --++ recommendations: true audience: Admin These are the basic parts of Teams and SharePoint and how they relate to each ot - **Parent site** - The SharePoint site that is created when you create the team. This site is used for file storage for all standard channels. All team owners and members have access to this site. -- **Channel site** - The SharePoint site that is created when you create a private or shared channel in a team. Only owners and members of the private or shared channel have access to this site.+- **Channel site** - The SharePoint site that is created when you create a standard (other than General), private or shared channel in a team. Only owners and members of the private or shared channel have access to this site. - **Public team** - A public team is a team that anyone in the organization can join. Public teams do not require a team owner to invite someone to the team. Contoso had a team called Mark 8 Project Team. This team has several standard ch The standard channels display as folders in the parent site. The private channel has its own channel site that is separate from the parent site. - + ## Teams-connected sites and channel types |